What problem does it solve?
Manually breaking down project plans, specs, or PRDs into disjointed, poorly tracked issues leads to missed dependencies, uneven work distribution, and deliverables that can't be demoed end-to-end. This skill eliminates that friction by enforcing a structured vertical slice decomposition workflow.
Core Features & Use Cases
- Tracer Bullet Vertical Slicing: Splits work into thin, end-to-end issues that cut through all integration layers (schema, API, UI, tests) instead of isolated single-layer tasks.
- Dependency & Task Classification: Clearly marks each issue as HITL (requires human input like design review) or AFK (can be implemented autonomously), with explicit blocker relationships to prevent workflow bottlenecks.
- Standardized Issue Templates: Generates consistent, ready-to-publish issue bodies with clear acceptance criteria, parent references, and blocked-by fields for seamless integration with your team's issue tracker.
- Use Case: When you have a new feature PRD for a todo app, this skill breaks it into demoable slices like "add user authentication end-to-end (DB schema + API + login UI + tests)" instead of separate, un-runnable tasks for each layer.
Quick Start
Use the to-issues skill to break down the attached product roadmap into independently assignable issues for the engineering team.