What problem does it solve?
Unstructured plans, specs, PRDs, or parent issues often leave development teams unsure how to split work into independent, executable tasks, leading to misaligned priorities, blocked workstreams, and wasted effort on poorly defined work items.
Core Features & Use Cases
- Vertical Slice Work Breakdown: Splits high-level work into tracer-bullet vertical slices, where each slice delivers a complete, demoable user behavior end-to-end rather than isolated technical layers.
- Standardized Issue Definition: Enforces a consistent structure for each issue, including clear titles, acceptance criteria, and dependency tracking, to eliminate ambiguity for developers or autonomous agents picking up work.
- Use Case Example: A product team with a new password reset feature PRD can use this skill to split the work into 4 small, testable slices that can be worked on in parallel without blocking each other, with clear acceptance criteria for each slice.
Quick Start
Use the issues skill to break down the attached new checkout flow PRD into 5 independent vertical slice issues with clear acceptance criteria and dependency links for each.