to-issues
Installation
SKILL.md
To Issues
Use this skill when the goal is to break already-shaped work into issue-tracker tickets that can be picked up independently. Favor tracer-bullet vertical slices: thin end-to-end slices that are demoable or verifiable on their own, with explicit dependencies and a clear distinction between AFK work and HITL work.
Use this skill when
- The user wants to turn a plan, spec, PRD, or approved feature idea into implementation issues.
- The user wants a PRD synthesized from current repository and conversation context, usually as the step before ticket breakdown.
- The next step is creating dependency-aware tickets rather than refining the product narrative.
- The work should be split into small vertical slices instead of broad layer-by-layer tasks.
- The output should either be published to the issue tracker or left as ready-to-paste issue bodies.
Do not use this skill when
- The codebase is not understood well enough to describe the slices responsibly — use
acquire-codebase-knowledge. - The user needs a reusable markdown handoff artifact rather than tracker-native issues — use
workflow-contracts. - The ask is still too vague to tell whether issue slicing is the right next step — use
reverse-prompt.