slicelisted

# /slice - Break a plan into vertical-slice issues Break a plan into independently-grabbable issues. Each issue is a tracer bullet, a thin slice cutting end-to-end through the layers this repository has, demoable or verifiable on its own. Which layers those are differs per repository: a web app has schema, API, UI, and test, while a harness or a library has an entry point, a decision, an output, and test. Settle their names in Phase 1 before cutting anything. ## Input Take the plan source from `$ARGUMENTS`. For an issue reference given as a number, URL, or path, fetch the body and comments via `gh issue view <N>`. If empty, work from a plan already in conversation context; if none, ask what to break down via AskUserQuestion. Check whether the source carries a `## Plan` section. When it does, the units are settled already, so distribute rather than draft. Phase 2 and where the issues go next both branch on this. ## Where the published issues go next When the source carried a `## Plan`, every slice is published carrying one too, so hand the issue number straight to the build workflow. When it did not, a sliced issue carries no `## Plan`, and handing it to the build workflow stops as no-plan. Take one slice at a time in the order below, starting from the one the user picks rather than driving every slice at once. 1. Draft the plan with `/think` 2. Run `/issue <number>`. The route that takes only a number is what moves that plan into the issue's `## Plan` section 3. Hand