brainstorming-validating

Name: brainstorming-validating
Availability: InStock
Author: ben-mad-jlp

Validate design documents for required sections before proceeding to rough-draft.

Updated Jan 12, 2026

Search Tags:#collaboration #requirements #validate #gate #design-review #design-document

Ready to run

npx skills add https://github.com/ben-mad-jlp/claude-mermaid-collab --skill brainstorming-validating

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming-validating
Source: https://github.com/ben-mad-jlp/claude-mermaid-collab/tree/main/skills/brainstorming-validating
Command: npx skills add https://github.com/ben-mad-jlp/claude-mermaid-collab --skill brainstorming-validating

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The VALIDATING phase runs the completeness gate to ensure the design is ready for implementation.

Core Features & Use Cases

Enforces presence and substantive content for required sections: Problem/Goal, Key Decisions, Diagrams, and Success Criteria.
Explicitly marks gaps and prevents progression until design gaps are resolved.
Use Case: A team verifies a design doc before starting implementation to avoid rework.

Quick Start

Review the current design document at .collab/<name>/documents/design.md, confirm all required sections exist and contain meaningful content, and, if complete, proceed to the next phase by updating the session and design status accordingly.

Frequently Asked Questions about brainstorming-validating

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate that a design document is complete before starting implementation?▼

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.

What sections are required in a design document to pass a completeness gate?▼

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.

How do I prevent teams from moving to coding when design requirements are missing?▼

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.

When should I run a design review gate during a collaborative session?▼

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.

What happens if a design document fails the validation gate?▼

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.