to-speclisted

Turn an approved planner.md into a slice-ready spec for a large ticket — the problem and the solution in user terms, the testing seam that proves each behaviour, and the behaviour boundaries to slice along. Runs inside the /start-ticket DECOMPOSE path, after the planner set slice-count > 1 and you approved the plan, and before /to-tickets. It is a thin transform of briefs that already exist: no interview, no re-exploration of the codebase. Not for a normal single-slice ticket.
konstantinos-malavazos/claude-code-playbook · ★ 2 · AI & Automation · score 68

Install: claude install-skill konstantinos-malavazos/claude-code-playbook

# to-spec — plan → slice-ready spec > Prior art: Matt Pocock's `to-spec` skill (MIT), upstream-renamed from `to-prd`. This is an > adaptation, not a copy. Two differences: it interviews nobody and re-explores nothing, > because the plan is already approved and `@context-gatherer` already swept; and it writes > an internal file, never an issue published to a tracker. ## When this runs Only in the `/start-ticket` **decompose path** — the planner set `slice-count > 1` and you approved the plan. On a single-slice ticket this skill does not run and the pipeline proceeds as normal. The path is [docs/shared/09](../../../docs/shared/09-decompose-path.md). ## Inputs — read these three, and nothing else - `<workspace>/.claude/handoffs/<TICKET-ID>/planner.md` — the approved plan: design, layer allocation, steps, risk, `## Open questions for grilling`. **Do not duplicate it.** - `<workspace>/.claude/handoffs/<TICKET-ID>/context-gatherer.md` — domain vocabulary, rulings, blast radius. Reuse its words so the spec speaks the project's language. - `<workspace>/.claude/handoffs/<TICKET-ID>/ticket-analyzer.md` — the acceptance criteria, verbatim. ## What this adds — the only reason it exists The plan already holds the *how*: files, symbols, layers, commits. This spec adds the two things `/to-tickets` needs in order to cut good slices. 1. **Testing seams** — where each behaviour is verified. Read `## Testing seams` in the repo's `CLAUDE.md` and name the produce/verify step or t