to-issues

To break a PRD into actionable GitHub issues, convert the spec into thin, end-to-end vertical slices using a tracer-bullet approach, then publish each slice as an independently-grabbable issue with explicit dependencies.

Tracer-bullet vertical slicing is an issue breakdown technique that cuts thin, end-to-end slices across schema, API, UI, and tests, ensuring each issue maintains full integration coverage rather than grouping tasks by architectural layer.

Plan human-in-the-loop (HITL) versus away-from-keyboard (AFK) issue tickets by evaluating slice granularity, flagging slices needing human decisions as HITL, and marking autonomous, independently-mergeable slices as AFK during the planning phase.

The best way to sequence issue publishing is by identifying blockers and dependencies across the vertical slices, then drafting an ordered list of issues that respects these constraints before publishing them to the project tracker.

Yes, you need an existing plan, spec, or PRD as input context to generate triage-ready implementation tickets, as the breakdown process requires collecting this context to propose slice granularity and shared contract guidance.

Vertical slices prevent loss of end-to-end intent during dependency planning by ensuring each issue independently cuts across schema, API, and UI, unlike layer-based breakdown which often fragments execution context and obscures integration blockers.