to-issues

To break a PRD into trackable issues, you provide the plan reference and the Skill drafts tracer-bullet vertical slices that map end-to-end across project layers, then publishes them to your issue tracker using a standard template.

Tracer-bullet vertical slices in issue tracking are independently-grabbable work increments that map end-to-end across project layers, enabling precise progress tracking from concept to delivery rather than splitting work by horizontal components.

You convert a product spec into executable tickets through guided context gathering, vertical-slice drafting, blocker validation, and publishing focused issues to your tracker with a consistent template for the lifecycle.

Yes, this creates issues that span multiple project components by drafting vertical slices across project layers, ensuring each ticket is an independently-grabbable end-to-end slice rather than a isolated frontend or backend task.

The best way to structure issue tracking for a new plan is using tracer-bullet vertical slices, which validate blockers early and provide consistent templates to trace implementation progress from concept to delivery.

You should avoid vertical slices when a plan requires horizontal foundation work first or lacks defined end-to-end layers, as this method relies on mapping independently-grabbable slices across all project components simultaneously.