create-spec

To decompose a feature plan into parallel tasks, you transform planning conversations into a structured set of self-contained task files organized into safe execution waves. This prevents file conflicts and enables multiple agents to implement work independently.

You structure feature specifications by generating a specs/{feature}/ folder containing a README, requirements, action-required, and tasks/ directory. Tasks are organized into sequential waves to ensure safe parallel execution without overlapping file modifications.

Wave-based task decomposition is a planning mechanism that breaks a feature into atomic, self-contained work items organized into sequential execution waves. This structure allows multiple agents to implement tasks in parallel within a wave while safely managing cross-wave dependencies.

Yes, you can generate a complete specs directory structure directly from a feature planning conversation. The process captures requirements and outputs a fully self-contained folder structure with detailed implementation instructions ready for automated execution.

No specific frameworks are required to organize atomic work items into execution waves. The process relies entirely on transforming your existing planning conversations into structured markdown files without any external dependencies.

You should avoid using parallel execution waves for task decomposition when feature requirements are ambiguous or when tasks cannot be isolated into atomic, self-contained work items without creating heavy cross-dependencies that would cause file conflicts during implementation.