to-issues

Breaking down a PRD into actionable issue tickets involves dividing the plan into tracer-bullet vertical slices that cut across all layers, then publishing them to an issue tracker using a standard template that blocks tasks by dependencies. The Skill gathers context, drafts slices, quizzes you, and publishes the issues.

Tracer-bullet vertical slices in backlog planning are complete, end-to-end implementation tickets that cut across all architectural layers. They ensure each issue is independently grabbable by different teams, allowing parallel development while maintaining a functional path through the system.

Creating independently grabbable issues for multi-team projects requires drafting vertical slices that are self-contained end-to-end. The Skill uses context from existing conversations or references to anchor definitions, then generates issues with a standard template and blocks by dependencies to manage cross-team coordination.

Converting existing specs into implementation tickets uses context-driven planning. The Skill anchors issue definitions using existing conversations or references, optionally explores the codebase, drafts the slices, quizzes you for validation, and publishes the issues without requiring a blank start.

The best way to structure work breakdown for a project issue tracker is using tracer-bullet vertical slices. This approach creates complete, end-to-end slices that cross all layers, ensuring each ticket is independently grabbable and properly blocked by its dependencies.

Vertical slices for issue breakdown may not suit projects lacking clear end-to-end paths or where layers cannot be crossed in a single ticket. The approach targets multi-team software projects needing independently grabbable issues, so isolated technical tasks or horizontal layer work may require a different breakdown strategy.