nextlisted

Shows the worklist board — everything that could be worked on, grouped by priority, annotated with effort, execution state, dependencies and whether triage is still owed by the human — followed by a shortlist of three to five things worth doing now. Use whenever the user asks what to work on next, wants an overview of open work, asks to see the board, the backlog by priority, or what is blocked, what needs their input, or what is worth doing now. Also `--triage` to set priorities on items that lack one and `--repair` to report convention debt to librarian. Triggers on 'what should I work on', 'what's next', 'show the board', 'what's blocked', 'what needs me', 'prioritize the backlog'.
supermodo/skills · ★ 0 · Web & Frontend · score 70

Install: claude install-skill supermodo/skills

# next — the worklist board > **Requires:** the sibling `protocols` skill (shared protocol masters) and a valid `skills.config.json` (create with the `config` skill). Missing either → halt with that exact pointer; never guess. > **Docs names come from config.** Every `docs/…` path below is the DEFAULT. Resolve folder and file names from `skills.config.json` → `docs.layout` (defaults when unset) before reading or writing — a path typed from memory writes a second tree beside the real one. See `../protocols/references/docs-convention.md`. > **Project rules.** Read `.supermodo/rules/next.md` if present, plus any > `.supermodo/rules/INDEX.md` rows naming `next` — that file IS this project's > next process and replaces the defaults below wherever they overlap. Contract: > `../protocols/references/rules.md`. Never in that file, so never switchable off: > never mutating docs or git, and an unset priority is unknown rather than P2. A THIN renderer. All selection semantics — priority, inheritance, execution state, ordering, effort bands, board format, suggestion rules — live in `../protocols/references/worklist.md`. Follow that master exactly; this file adds only invocation and handoff. Read `../protocols/references/worklist.md`, `../protocols/references/docs-convention.md` (the grammar it parses), `../protocols/references/questions.md` (for `--triage`) and `../protocols/references/reports.md` (how every run is persisted and published). Validate config FIRST per `../protocols/ref