sdd-tasks

To generate implementation tasks from architectural design documents, this skill converts specifications into phase-organized task lists. It reads design artifacts to produce actionable steps, estimate review complexity, and define testing boundaries.

Breaking down software architecture into phased execution plans involves transforming proposals into structured task breakdowns. This workflow organizes implementation steps, forecasts changed lines, and identifies high-risk changes requiring chained PRs.

Estimating workload and review complexity in Spec-Driven Development requires analyzing design documents to forecast changed lines. The skill enforces a 400-line review budget guard and identifies high-risk changes for safer execution.

Yes, converting software specifications into task lists requires integration with an orchestrator. This integration reads proposal, spec, and design artifacts to accurately generate phase-based implementation steps and rollback boundaries.

Yes, task planning defines testing boundaries and rollback limits by analyzing approved feature designs. It generates detailed execution orders that include specific testing requirements and clear rollback boundaries for safe implementation.

Automated task breakdown should not be used when lacking approved architectural design documents. The skill requires existing proposal, spec, and design artifacts to generate accurate phase-organized implementation steps and workload forecasts.