sprint-boardlisted

Plans, writes and audits agile backlogs as markdown - epics, features and user stories - against a fixed template, with a scaffolder and a linter. Use when asked what the epics, features and stories should be for a goal, repo or product idea; when a product idea needs turning into a workable, sequenced backlog; when handed a part-built or blank-template board to complete, repair, sequence or audit; when stories lack acceptance criteria or sizing and need them challenged; when a milestone needs dependency-ordered sequencing; or when an item is too big for one iteration and needs splitting. A repo's own tasks/plan.md and todo.md are working docs, not boards, and stay with their own skills. Also on /sprint-board.
thefilesareinthecomputer/dotagents · ★ 0 · Data & Documents · score 72

Install: claude install-skill thefilesareinthecomputer/dotagents

# sprint-board Turns a goal, a codebase, a product idea or a half-drafted board into a sequenced backlog of epics, features and stories written into the user's own template, ready to copy into a tracker. ## The four modes Identify the mode before doing anything. Greenfield, Partial and Maintenance differ at Step 1 only; Audit is a different job. | Mode | Trigger | Step 1 becomes | |---|---|---| | **Greenfield** | A goal, repo, product idea or technology with no backlog yet | Intake: establish the end state and constraints | | **Partial** | A board part-built or handed down, with real IDs and an incomplete spine | Baseline: read every item, infer the intended end state, list what is missing | | **Maintenance** | A vault or repo where these files are the standing record | Reconcile: diff the board against the current end state | | **Audit** | Validate, fact-check, proofread or review a board without extending it | Skip to Step 7 | **Audit writes no new items.** Asked to check, validate, fact-check or proofread, run `board_lint.py`, then `references/audit.md`, then - if a grounding source is available - verify each claim about what exists today against it. Report findings against `file:line` and let the user decide what to change. Silently repairing what you were asked to review destroys the record of what was wrong, and a story you rewrite is one nobody gets to reject. Extending an audited board is a separate pass the user asks for. Partial is the most common and the most