brainstorming

To turn vague product requirements into a validated design specification, use guided collaborative dialogue to clarify constraints and success criteria. This process proposes 2-3 approach trade-offs and refines intent through one-question-at-a-time discovery before writing any code.

Documenting software architecture trade-offs in git involves writing validated design specifications into markdown files. The design is written to docs/plans/YYYY-MM-DD-<topic>-design.md and committed to git to ensure architecture decisions are tracked alongside code changes.

Refine feature ideas through collaborative planning by asking one question at a time, using multiple-choice options when helpful. This reduces ambiguity, prevents missed assumptions, and incrementally builds the design in 200-300 word sections validated after each step.

Yes, collaborative brainstorming works for component design and behavior change tasks. It grounds the design in current project state by reviewing files and recent changes, fitting any feature creation where requirements and constraints must be clarified before implementation.

Compare solution approaches for requirements gathering by proposing 2-3 distinct options with clear trade-offs. The process selects a recommended direction based on your specific constraints to ensure the final architecture aligns with project realities.