to-issues

To break a product spec into verifiable GitHub issues, the skill processes your PRD and drafts tracer-bullet vertical-slice tickets that cut through all integration layers like schema, API, UI, and tests for end-to-end validation. It presents these slices for interactive user review and iterates until granularity is approved.

Vertical-slice issues are tracer-bullet work items that cut through all integration layers including schema, API, UI, and tests rather than splitting work by component type. This breakdown method creates independently grabbable engineering issues that can be implemented and validated end-to-end.

You organize implementation tickets by dependency order by having the skill queue issue creation sequentially, populating each ticket with decision-rich acceptance criteria and blockers. This dependency-aware publishing ensures engineering execution flows correctly from foundational to advanced vertical slices.

You can tag issue breakdown tickets as HITL requiring human interaction like reviews or decisions, or AFK implementable without human interaction. This AFK/HITL classification happens during the interactive user verification phase before publishing the final GitHub issues.

The issue breakdown process requires an existing plan, spec, or PRD as input, but it can optionally explore your codebase to gather additional context. It uses this gathered context to draft vertical-slice issues, quizzing you interactively until dependencies and HITL/AFK tags are approved.