to-issues
To Issues
Break a plan, spec, or conversation into issues — tracer-bullet vertical slices, each declaring the issues that block it.
The issue tracker and triage label vocabulary should have been provided to you — run /setup-agent-skills if not. Setup defaults to existing Beads state, then local .scratch; it never chooses a hosted tracker from the Git remote without the user's explicit approval.
Process
1. Gather context
Work from whatever is already in the conversation. If the user passes a spec path, issue number, URL, or local issue path, fetch it from the configured tracker and read its full body and comments.
2. Explore the codebase when needed
If the codebase has not already been explored, inspect enough of it to understand the current implementation. Issue titles and descriptions should use the project's domain glossary vocabulary and respect ADRs in the area being changed.
Look for prefactoring that would make the implementation easier: make the change easy, then make the easy change.