Askit backlog

Skill product-on-purpose/agent-skills-toolkit/skills/askit-backlog

Toolkit and Standard for building, grading, and scaling cross-agent skill libraries (Claude Code + Codex) to a tiered Bronze/Silver/Gold quality bar.

Install

npx -y skills add product-on-purpose/agent-skills-toolkit --skill askit-backlog

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.2 KB, as published. Nobody here has run it

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.

When to use

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

intake mode

Decide which backlog: a new component (new-components.md) or a change to an existing one (enhancements.md).
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.
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

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

prune mode

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.