brainstorming-validating

To validate a design document before implementation, run the completeness gate to verify required sections (Problem/Goal, Key Decisions, Diagrams, Success Criteria, Out of Scope) are present and non-empty. The gate prevents progression to rough-draft until all content gaps are resolved.

To pass a completeness gate, a design document must contain substantive, non-empty content in the Problem/Goal, Key Decisions, Diagrams, and Success Criteria sections. It also checks for an Out of Scope section to ensure full readiness before implementation.

To prevent teams from moving to coding with missing requirements, apply a validation gate during collaborative design sessions that blocks phase advancement. It explicitly marks detected design gaps and prevents progression until those gaps are resolved.

Run a design review gate during collaborative sessions right before transitioning to the rough-draft or implementation phase. This validates that all design document sections are complete, updating the session status on success and preventing advancement on failure.

If a design document fails the validation gate, the tool explicitly marks the missing or empty sections and prevents progression to the next phase. The design status remains unchanged until those identified gaps are resolved.