to-issues
/to-issues
Break a plan into independently-grabbable issues using vertical slices (tracer bullets), and leave behind a real dependency tree on the tracker, not prose that claims one.
An improvement on Matt Pocock's
to-issues. Same tracer-bullet slicing and issue template; the addition is a mandatory final step that wires the blocked-by/parent edges into native GitHub sub-issues and dependencies, so the tracker renders the real tree instead of leaving "Blocked by #N" as dead prose.
The issue tracker and triage label vocabulary should have been provided to you. If not, set them up before publishing.
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.