agentsclimarketplace
Sign in

Next

Skill mirkobozzetto/arsenal/plugins/next/skills/next

Report unfinished prd/rfc/ship work in this repo and the exact command to resume each, ranked by what to do now. Use when the user asks "what's next", "what's left", "where do I resume", "/next", "la suite", or to re-orient after a context reset. Reads artifact frontmatter as the source of truth; never implements.From its SKILL.md

Install
npx -y skills add mirkobozzetto/arsenal --skill next

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

2 things to look at

  • 12 stars12 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.
  • runs commandsInstructs the agent to run 1 command, including `node <this-skill-dir>/scripts/scan.cjs [--all] [<extra-repo-roots>]`.

SKILL.md

2.7 KB, 609 tokens by cl100k_base, as published. Nobody here has run it

<objective> Answer "what is left to do and how do I resume it" by scanning this repo's prd/rfc artifacts, classifying open vs done from their frontmatter, and emitting the single best next command. Read-only. This skill routes; it never builds (that is ship). </objective>

<how_it_works> The state lives in the artifacts themselves, not a separate ledger:

  • prd: docs/prd/<slug>/prd.md frontmatter status (draft -> ready -> shipped) + tasks.md checkboxes for progress.
  • rfc: docs/rfcs/.../RFC.md frontmatter status (Draft -> Review -> Accepted -> shipped).
  • OPEN = prd ready/in_progress or rfc Accepted. DONE = shipped/superseded/Rejected (hidden). WIP = still authoring (draft/Review).
  • resume_cmd in frontmatter wins; otherwise it is derived from the path (/ship <folder-or-RFC.md>).

Because the board is DERIVED on read, it self-prunes the instant ship flips a status. No file to keep in sync. See references/state-contract.md for the exact frontmatter fields prd/rfc/ship maintain. </how_it_works>

<steps> 1. Run the scanner from the repo root. Locate `scripts/scan.cjs` under THIS skill's base directory (shown when the skill loads); when installed as a plugin it is `${CLAUDE_PLUGIN_ROOT}/skills/next/scripts/scan.cjs`: `node <this-skill-dir>/scripts/scan.cjs [--all] [<extra-repo-roots>]` - default: the OPEN board + the recommended `Next:` command. - `--all`: also show in-authoring and done items. - `--json`: structured output (for tooling). - pass extra repo paths to scan sibling repos in one shot. 2. Render the result as-is. Keep it short. Do NOT re-read every artifact body; the frontmatter scan is enough. 3. If a feature argument is given, open that artifact (prd.md + tasks.md, or RFC.md) and report: status, done-vs-remaining tasks, the next unchecked task, and the why from the spec. 4. Recommend ONE next action: the top-ranked open item's resume command. Hand off; do not run it. </steps> <notes> - Stale "Accepted"/"ready" items that are actually already built mean the loop was not closed historically (ship now flips status on finish). Offer a one-time reconcile: set `status: shipped` on the already-done artifacts so the board reflects reality. - The same scanner backs the SessionStart hook (`--banner`), so the auto clock-in and `/next` never diverge. </notes>

What ships with it: 2 files

9.7 KB alongside SKILL.md, 1 of them executable

references/

scripts/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.