What problem does it solve? Turning an approved spec-driven design into concrete, ordered implementation work is error-prone: tasks end up vague, unordered, or too large to review. This Skill converts a change's proposal, specs, and design into a structured tasks.md with dependency-ordered phases and a review workload forecast. ## Core Features & Use Cases - Phased Task Breakdown: Produces hierarchical, dependency-ordered tasks (1.1, 1.2, 2.1...) across Foundation, Core, Integration, Testing, and Cleanup phases, each referencing concrete file paths. - Review Workload Forecast: Estimates changed-line volume against a 400-line review budget and recommends chained or stacked PR splits with a chosen delivery strategy (ask-on-risk, auto-chain, single-pr, exception-ok). - Multi-Mode Persistence: Supports engram, openspec, hybrid, and none artifact store modes, reading upstream artifacts and persisting the tasks artifact accordingly. - Use Case: After an orchestrator completes proposal, spec, and design phases for a new authentication feature, this sub-agent generates a tasks.md listing exact files to create, TDD red-green-refactor steps, and a PR split plan before implementation begins. ## 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.
