to-issues
Break a plan into independently-grabbable vertical-slice issues for your project tracker.
- Fetches context from conversation or referenced issues, optionally explores codebase to align with project vocabulary and architecture decisions
- Breaks plans into tracer-bullet slices that cut end-to-end through all layers (schema, API, UI, tests), not horizontal layer-by-layer slices
- Classifies each slice as HITL (requires human decision/review) or AFK (implementable without interaction), preferring AFK where possible
- Presents proposed breakdown for user review and iteration before publishing issues to the tracker in dependency order
To Issues
Break a plan into independently-grabbable issues using vertical slices (tracer bullets).
The issue tracker and triage label vocabulary should have been provided to you — run /setup-matt-pocock-skills if not.
Process
1. Gather context
Work from whatever is already in the conversation context. If the user passes an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker and read its full body and comments.
2. Explore the codebase (optional)
If you have not already explored the codebase, do so to understand the current state of the code. Issue titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.
Look for opportunities to prefactor the code to make the implementation easier. "Make the change easy, then make the easy change."