What problem does it solve? Turning an approved spec-driven development (SDD) design into concrete, ordered implementation work is error-prone: tasks end up vague, unordered, or missing test coverage. This Skill converts a change's proposal, specs, and design into a structured tasks.md with dependency-ordered phases and verifiable steps. ## Core Features & Use Cases - Phased Task Breakdown: Produces hierarchical, dependency-ordered tasks (1.1, 1.2, 2.1...) across foundation, implementation, integration, testing, and cleanup phases. - Review Workload Forecast: Estimates changed-line volume against a 400-line review budget and recommends chained or stacked PR splits with test commands, runtime harnesses, and rollback boundaries. - Multi-Mode Persistence: Supports engram, openspec, hybrid, and none artifact store modes, reading prior SDD artifacts and persisting the tasks artifact accordingly. - Use Case: After an orchestrator completes the design phase for a new authentication feature, this sub-agent generates a tasks.md where every threat-matrix case becomes a RED test task before its production task, with a PR split plan if the change exceeds the review budget. ## Quick Start Delegate to the sdd-tasks sub-agent with the change name, artifact store mode, and delivery strategy to generate the implementation task breakdown for the current SDD change.
