feature-plan

Feature planning before coding prevents scope creep by enforcing upfront documentation of requirements and architecture. You create a structured plan document capturing design decisions, types, algorithms, and tasks to ensure architecture clarity across teams.

Wave-based task planning coordinates multiple teams by breaking feature development into phased design and execution waves. It reduces cross-functional friction by enforcing a phase-by-phase verification workflow aligned with research-backed decisions.

Feature design documentation requires a structured plan at docs/plans/<feature-name>.md. It enforces explicit sections for design, types, algorithms, parameters, constants, tasks, and verification to guide development and maintain architectural alignment.

Architecture-first planning supports multiple teams by establishing a canonical docs/plans schema and wave-based task planning. This governance ensures phase-driven verification and reduces cross-functional friction during feature implementation.

Documenting project requirements before implementation is best handled by creating a canonical plan document. It enforces fidelity verification against research outcomes, capturing parameters, constants, and algorithms to prevent misaligned design and duplicated effort.