What problem does it solve? Turning a feature specification and implementation plan into an actionable, dependency-ordered task list is error-prone manual work. This Skill automates the tasks phase of the spec-kit Companion pipeline, producing a tasks.md file where each user story is an independently testable increment. ## Core Features & Use Cases - Phased Task Generation: Reads spec.md, plan.md, data-model.md, and contracts to produce tasks.md organized into Setup, Foundational, per-story, and Polish phases. - Explicit Dependency Waves: Groups tasks into ordered waves with [P] markers for independent parallelizable work and join lines showing where work must wait. - Size-Aware Budgeting: Reads the recorded change size from .spec-context.json and produces a lean task list for simple changes, trimming ceremony while keeping precise task lines. - Requirement Traceability: Captures a requirement-to-task coverage map via the write-context.py script so each FR-X maps to concrete task IDs. - Use Case: After running the plan step on a new feature, invoke this Skill to generate a tasks.md where the P1 user story forms the MVP slice, each task names its exact file, and validation against Success Criteria is owned by exactly one phase. ## Quick Start Run the speckit companion tasks step to generate a dependency-ordered tasks.md from my current spec and plan.
