AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Askit Backlog

skill-product-on-purpose-agent-skills-toolkit-askit-backlog · by product-on-purpose

Creates, triages, and prunes a plugin's two backlogs (new-component proposals and enhancements) to the Advanced Skill Library Standard. Use when capturing a new-component proposal through the why-gate, prioritizing backlog items, or removing stale or completed entries.

↗ Website ↗ Repository
— No reviews yet
0 installs
3 views
0.0% view→install

Install

$ agentstack add skill-product-on-purpose-agent-skills-toolkit-askit-backlog

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Askit Backlog? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

askit-backlog

Purpose

Maintain the two local-first backlogs the Standard defines (sec 7.1): docs/internal/backlog/new-components.md (proposals to add a skill, command, subagent, hook, and so on) and docs/internal/backlog/enhancements.md (changes to existing components). Three modes: intake captures a proposal through the why-gate; triage prioritizes and routes; prune removes stale or completed items. Authoring depth is in [references/backlog-workflow.md](references/backlog-workflow.md).

When to use

When the user proposes a new component, requests an enhancement, or wants to review, prioritize, or clean the backlog.

intake mode

  1. Decide which backlog: a new component (new-components.md) or a change to an existing one (enhancements.md).
  2. Apply the why-gate to a new-component proposal: is it warranted? is it a duplicate of an existing component, or really a mode of one? what tier and agent-targets? If it fails the gate (a duplicate, or a would-be mode), record the rationale and route it to enhancements instead.
  3. Record the item. New-components: proposed name, component type, target tier, agent-targets, rationale, status. Enhancements: the target component, the change, a why, and a how-to-apply.

triage mode

  1. Review open items; assign priority and, for enhancements, the target component or phase.
  2. Re-route mis-filed items (a "new component" that is really a mode becomes an enhancement).

prune mode

  1. Remove items that shipped (now in the CHANGELOG) or that are stale or rejected, recording why.

Scope

Two backlogs, local-first and version-controlled (sec 7.1): RECOMMENDED at Bronze, REQUIRED at Silver+. The why-gate keeps the new-components backlog from collecting duplicates and would-be modes; consolidation (one skill per component type, modes over micro-skills) is the default answer, per the toolkit's own packaging decision.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills