sdd-spec-tasks

To generate implementation tasks from technical specifications, this Skill translates approved requirements and design components into executable work items. It scopes tasks to feature directories and utilizes project-wide context to ensure full requirements coverage.

The best way to break down spec-driven development designs is to map design components into hierarchically structured work items. This process ensures tasks are properly sized for 1-3 hours of work and logically sequenced for immediate developer execution.

Yes, you can scope generated tasks to specific feature directories within `docs/tasks/`. The Skill organizes the actionable work items into these directories while pulling project-wide context from `docs/steering/`.

To ensure tasks are appropriately sized, the Skill automatically scopes and structures generated work items to fit within a 1-3 hour execution window. This sizing happens during the translation of approved specifications into granular tasks.

Yes, spec-driven development task generation utilizes project-wide context from `docs/steering/` to accurately map requirements. This ensures the generated executable work items align with the broader project architecture and constraints.

You need to map requirements into executable work items after a feature's design is approved. This bridges the gap between design and execution by creating a clear, step-by-step implementation plan for developers.