to-issues

You can break down a PRD into actionable issue slices by generating tracer-bullet vertical slices that span schema, API, UI, and tests. The output is a set of independently-grabbable issues with standardized acceptance criteria and dependencies ready for publication.

Tracer-bullet vertical slices are end-to-end issue segments that cut across all integration layers including schema, API, UI, and tests. They ensure each independently-grabbable issue delivers functional value across the entire stack rather than focusing on a single horizontal layer.

Yes, you can generate standardized issue templates with acceptance criteria and clear blocking relationships directly from a design document. The process enforces a consistent issue body format to enable rapid publishing to your issue tracker.

You can handle human-in-the-loop dependencies by generating HITL slices that explicitly guide blockers and dependencies. The breakdown supports both HITL and AFK slices, ensuring issues requiring immediate human input are properly flagged alongside automated tasks.

Yes, the issue breakdown process prompts for user validation before publishing to a tracker. This ensures that the generated vertical slices, acceptance criteria, and dependency relationships are reviewed and confirmed prior to creating the final issues.

Vertical slice breakdown should be used when you need independently-grabbable issues that span end-to-end integration layers like schema, API, UI, and tests. It is ideal for agile planning where delivering functional tracer-bullet slices is preferred over isolated horizontal layer tasks.