to-issues
To Issues
Break a plan into independently-grabbable issues using vertical slices (tracer bullets).
The issue tracker should be accessible via gh. If label vocabulary is needed, check the project's AGENTS.md or issue templates.
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.
3. Draft vertical slices
Break the plan into tracer bullet issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.
More from camacho/ai-skills
bail
Reflects, updates GitHub Issue, closes PR if open, cleans up worktree/branch.
566plan-review
Auto-assembles review panel using deterministic rules, dispatches agents against plan file, collects verdicts.
547archive
Fills Outcomes & Learnings in a plan file and renames it to .done.md.
542orient
Fetches issue context, auto-detects task type, maps to branch prefix, presents brief.
537capture
Creates a draft GitHub Issue with triage label from natural language description.
535reflect
Use after merging a branch or completing a task to consolidate learnings into memory layers, close out issues, and verify the phase gate.
500