next

<objective> Answer "what is left to do and how do I resume it" by scanning this repo's brief/propose 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: - brief: `docs/brief/<slug>/brief.md` frontmatter `status` (draft -> ready -> shipped) + `tasks.md` checkboxes for progress. - propose: `docs/proposals/.../PROPOSAL.md` frontmatter `status` (Draft -> Review -> Accepted -> shipped). - OPEN = brief `ready`/`in_progress` or propose `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-PROPOSAL.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 brief/propose/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. ...