plan

To decompose software specifications into atomic development tasks, apply this skill to your SPEC.md to generate structured plans with wave groupings, role assignments, and clear task boundaries. It ensures each task includes spec references, file lists, acceptance criteria, and test commands.

Wave grouping in agentic workflow task planning organizes atomic tasks into dependency-free waves for concurrent execution. This approach prevents vague assignments and ensures parallelizable work streams by structuring tasks so independent items can be executed simultaneously.

To generate a task plan with role assignments from a spec file, process your approved SPEC.md through the planner. It assigns appropriate agent roles to each atomic task and outputs PLAN.md, PROGRESS.md, and an RFC for human review before execution.

Yes, you can parallelize development tasks from a high-level specification by decomposing milestones into atomic tasks and organizing them into dependency-free waves. This creates parallelizable work streams with detailed acceptance criteria and file lists.

When creating atomic task plans from specs, you get PLAN.md, PROGRESS.md, and an RFC for human review. Each atomic task within these outputs includes spec references, file lists, acceptance criteria, and test commands for clear execution boundaries.

You need to create atomic task plans in an agentic development workflow during Phase 3, after you have an approved SPEC.md. This phase transforms high-level specifications into concrete, atomic tasks to prevent vague assignments before proceeding to execution.