brainstorming

To validate project requirements, you need a structured design workflow that explores project context, asks clarifying questions one at a time, and proposes approaches with trade-offs. This process ensures goals and constraints are clarified before any coding begins.

A design doc is a formal markdown document logging project decisions and validated designs. You need one for complex, multi-step projects requiring design validation before coding, ensuring success criteria and constraints are formally reviewed.

Creating a design document involves examining existing project files and commits, running a clarification cycle to understand constraints, proposing 2-3 approaches, and writing the validated design to a dated spec file for a formal review loop.

Yes, a structured brainstorming workflow enforces requirements gathering by asking clarifying questions sequentially to understand purpose and constraints. It proposes approaches with trade-offs and manages a formal review loop before transitioning to implementation planning.

The best way to document design decisions is writing a formal design document to a dated specs markdown file after seeking approval on a proposed approach. This logs decisions and runs a spec-review loop to address issues before implementation.

Design validation stalls when a formal review loop is skipped or unresolved issues remain. A structured process re-dispatches the design doc until approved, ensuring all constraints are addressed before transitioning to implementation planning.