to-issues
To Issues
Break a plan into issues anyone can grab independently, cutting them as vertical slices (tracer bullets).
The issue tracker and triage label vocabulary should already have been handed to you — run /setup-skills if not.
Process
1. Gather context
Work from whatever's already in the conversation. If the user passes an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker and read the full body and comments.
2. Explore the codebase (optional)
If you haven't explored the codebase yet, do so to learn the current state of the code. Issue titles and descriptions should use the project's domain glossary and respect ADRs covering the area you're touching.
Look for chances to prefactor the code so the implementation lands more easily. "Make the change easy, then make the easy change."