to-issues

To break a PRD into vertical-slice issues, the work is decomposed into thin tracer-bullet slices that cut through schema, API, UI, and tests end-to-end, ensuring each issue is independently actionable and maintains end-to-end intent for execution and triage.

Tracer-bullet vertical slices are thin work segments that cut through all architectural layers—schema, API, UI, and tests—end-to-end, avoiding horizontal layer work, to ensure deliverables are independently grabbable and fully functional for tracking.

During issue decomposition, tickets are classified as AFK (automatable end-to-end) or HITL (Human-in-the-Loop) to identify slices requiring human interaction, such as design reviews or architectural decisions, distinguishing automatable work from manual tasks.

To publish decomposed issues with dependencies, a numbered breakdown is drafted for user approval first, then issues are published in dependency order with correct triage labels and blocker references attached to maintain execution sequence.

Yes, existing issue references can be ingested by fetching full issue details and comments from the context, allowing the breakdown to incorporate current tracker state and extract referenced issue context before drafting new tickets.