brainstorming-validating

# VALIDATING Phase

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

## Purpose

- Verify all required sections are present
- Check for completeness and clarity
- Ensure no TBDs or ambiguous items remain
- Gate the transition to rough-draft

## Required Sections

The design doc must contain all of these:

- [ ] **Problem/Goal** - Clear statement of what we're solving and why
- [ ] **Key Decisions** - At least one documented decision with rationale
- [ ] **At least one diagram** - Visual representation of architecture, flow, or UI
- [ ] **Success Criteria** - Measurable, testable criteria (not "works well")
- [ ] **Out of Scope** - Explicit boundaries on what this work does NOT include

## Gate Check Process

```bash
# Read design doc
cat .collab/<name>/documents/design.md

# Verify each required section exists and has content
# If any section is missing or empty, do NOT proceed
```

For each section, verify:
1. Section header exists
2. Section has substantive content (not just placeholder text)
3. Content is specific, not vague

## Single-Item Mode (VALIDATING)

When `currentItem` is set in collab-state.json:

Check item has all required fields filled:
- Problem/Goal filled
- Approach filled
- Success Criteria filled

**If validation fails:** Return to DESIGNING to fill gaps

**If validation passes:**
```
DISPLAY: "Item documented. Returning to work item loop."
RETURN to collab skill
```

**Important:** In single-item mode, do NOT:
- Run the full completeness gate
- Transition to rough-draft
- Update collab-state.json phase

The collab skill manages the work item loop and will mark the item as documented after this skill returns.

## If Gate Fails

1. Identify which sections are incomplete
2. List the specific gaps found
3. Return to DESIGNING phase to fill gaps
4. Do NOT proceed to rough-draft until all sections pass

**Example failure message:**
```
Completeness gate failed:

Missing or incomplete:
- [ ] Key Decisi