brainstorming

To turn ambiguous ideas into validated design specifications, clarify user intent, requirements, constraints, and success criteria through one-question-at-a-time discovery, then generate multi-approach design options with trade-offs before writing a final plan.

The best way to document feature design plans for an active codebase is by incrementally validating design sections and writing the finalized, dated plan file to a docs/plans directory with a git commit to ensure careful alignment.

Incremental design validation during requirements discovery works by presenting the design in 200–300 word sections and checking alignment after each section to ensure the translation of ambiguous ideas into a clear, implementable design.

You can explore multiple design approaches by generating 2–3 options and recommending a preferred path with trade-offs before finalizing the design documentation and writing a dated plan file.

Requirements discovery supports implementation handoff for component planning by writing validated design documentation to docs/plans with a git commit and then prompting for implementation planning when ready to proceed.