What problem does it solve? Turning a large plan or spec document into actionable work items is hard: tickets often end up as horizontal layer slices that cannot be demoed independently, or dependencies between tickets are unclear. This Skill decomposes a plan into independently-grabbable vertical-slice tickets with explicit blocking edges. ## Core Features & Use Cases - Vertical Slice Decomposition: Splits work into tracer-bullet tickets that cut through every layer (schema, API, UI, tests) so each ticket is demoable on its own. - Dependency Modeling: Assigns blocking edges to every ticket and renders a Mermaid dependency graph grouped by phase (Foundation, Core Abstractions, Implementations, Services, UI & Deploy). - Deep Module Awareness: Respects module boundaries from the spec, ensuring deep modules get their own early tickets and are never split or bundled into service tickets. - Use Case: After writing a feature spec, ask the Skill to convert it into tickets; it quizzes you on granularity and dependencies, then publishes a numbered ticket set with acceptance criteria and a dependency graph. ## Quick Start Ask the AI to break the attached spec document into implementation tickets using the to-tickets skill.
