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 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, implementation, 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 test commands, runtime harnesses, and rollback boundaries per work unit. - Multi-Mode Persistence: Supports engram, openspec, hybrid, and none artifact store modes, reading upstream artifacts and persisting the tasks artifact accordingly. - Use Case: An orchestrator delegates planning for a new change; the sub-agent reads the design, emits a tasks.md with RED-test-first tasks for every threat-matrix case, and returns a summary with the recommended PR chain strategy. ## Quick Start Ask the orchestrator to run task planning for your SDD change so it delegates to the sdd-tasks sub-agent and produces a tasks.md breakdown.