to-issues

To convert a PRD into issue-tracker tickets, the Skill transforms product requirements into independently-grabbable tickets using tracer-bullet vertical slices. It breaks down work into end-to-end slices that cut through schema, API, UI, and tests so each piece is demoable.

Tracer-bullet vertical slicing is an issue breakdown technique that cuts work into thin, end-to-end slices through schema, API, UI, and tests. This ensures each slice is independently demoable or verifiable rather than split horizontally by technical layer.

To map dependencies when creating tickets, the Skill publishes issues in dependency-aware sequencing with blocked-by relationships. It uses an issue body template and triage label vocabulary to ensure blocked work is explicitly clear during project planning.

Yes, you can classify issue slices as human-in-the-loop (HITL) or fully automatable/mergeable (AFK). The Skill marks slices requiring architectural or design reviews as HITL, while leaving fully automatable execution slices as AFK to optimize workflow.

Yes, the issue breakdown process requires user approval iteration. The Skill mandates human-in-the-loop decisions on end-to-end slice definitions and dependency-aware sequencing before publishing templated issues to your tracker.

The best way to break down a spec into independently implementable issues is using dependency-aware sequencing with vertical slices. This preserves end-to-end intent through templated issue creation with triage labels and blocked-by relationships for clear execution tracking.