feature-plan

To decompose a design doc into implementation tasks, load your design document into the .feature/state/design directory and run the planning phase. It analyzes dependencies and file conflicts to produce a wave-ordered plan with domain-agent assignments.

Yes, you need an existing design document placed in .feature/state/design before generating a wave-ordered implementation plan. The tool reads this design state to analyze dependencies, assign domain agents, and detect file conflicts for task decomposition.

Parallel execution and file conflict analysis evaluates task dependencies within the decomposed design to identify tasks that can run simultaneously. It assigns domain agents to each task and flags potential file conflicts to prevent concurrent modification issues.

Yes, state management relies on python3 scripts/feature-state.py to load and manage the design document state. This script enforces design dependencies and ensures the generated plan artifact correctly feeds downstream implementation steps.

If design dependencies are unresolved, the tool enforces these dependency chains during wave ordering and will not generate a valid plan artifact. It analyzes parallelism and file conflicts strictly based on the established design dependencies to prevent execution errors.