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, verifiable tasks (1.1, 1.2, ...) organized into 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 focused test commands, runtime harnesses, and rollback boundaries. - Multi-Mode Persistence: Supports engram, openspec, hybrid, and none artifact store modes, reading dependencies and persisting the tasks artifact accordingly. - Use Case: After an orchestrator completes the design phase for a new API feature, this sub-agent generates tasks.md with RED-test-first tasks derived from the threat matrix, plus a PR-chaining recommendation when the change exceeds the review budget. ## Quick Start Ask the orchestrator to run task planning for your approved SDD change so it delegates to the sdd-tasks sub-agent and produces a tasks.md breakdown.
