to-issues

To break a PRD into actionable engineering tickets, you decompose the spec into thin vertical slices that span schema, API, UI, and tests, producing issue drafts with clear acceptance criteria and dependency sequencing.

Tracer-bullet slicing in issue tracking is a planning technique that divides a product spec into thin, end-to-end vertical slices spanning schema to UI, ensuring each issue is independently grabbable and shippable by the engineering team.

To map dependencies and blockers when creating issues from a plan, you sequence the tracer-bullet slices in strict execution order, tagging prior issues as blockers so the tracker can publish them in a ready-to-run dependency sequence.

Yes, you can distinguish between automatable tasks and human-in-the-loop decisions in issue drafts by explicitly categorizing each vertical slice, separating fully automatable work from slices requiring manual human decisions.

Yes, this approach works for generating tickets ready for a project issue tracker by producing complete issue bodies equipped with acceptance criteria and blocker mapping, formatted specifically for direct publishing to your tracking system.