What problem does it solve? Large specs with multiple outcomes are hard to deliver and review as one unit. This Skill turns an approved spec into the fewest independently deliverable vertical tasks, each with observable acceptance criteria, genuine blockers, and only risk-justified review checkpoints. ## Core Features & Use Cases - Outcome-based task splitting: Proposes the fewest independently usable and verifiable outcomes instead of splitting by CRUD actions or technical layers, and keeps a single coherent workflow as the spec itself. - Approval-gated handoff: Presents the complete task map for user approval before writing any task files to docs/specs/<slug>/tasks/ using a structured template. - Revision and supersede handling: Preserves completed task history, marks replaced tasks as superseded with revision evidence, and moves blocker references to approved replacements. - Use Case: Given a spec covering personal todos, collaboration, and reminders, the Skill proposes three vertical tasks with dependency blockers, waits for approval, then writes one task file per deliverable. ## Quick Start Ask the assistant to split the approved spec at docs/specs/<slug>/spec.md into independently deliverable tasks and show the breakdown for approval.
