What problem does it solve?
Manually breaking down project plans, specifications, or product requirement documents (PRDs) into well-scoped, independently assignable issue tracker tickets is time-consuming and often leads to inconsistent, poorly defined work items that are hard to prioritize and implement.
Core Features & Use Cases
- Vertical Slice Breakdown: Splits work into tracer bullet issues, each delivering a thin, end-to-end slice through all integration layers (schema, API, UI, tests) instead of horizontal layer-specific chunks.
- HITL/AFK Classification: Labels each slice as either human-in-the-loop (requiring architectural decisions or design reviews) or AFK (implementable and mergeable without human input) to prioritize work appropriately.
- Project-Aligned Issues: Ensures issue titles, descriptions, and acceptance criteria use the project's domain glossary and respect existing architectural decision records (ADRs) for consistency.
- Use Case: A product manager with a new feature PRD can use this skill to generate a set of ready-to-publish, properly scoped issues for their engineering team, each with clear acceptance criteria and dependency tracking.
Quick Start
Use the to-issues skill to break down the attached Q4 feature PRD into a set of trackable issues for the engineering team.