verify-phase

# Verify Phase

## Overview

Checks if rough-draft output aligns with original design. Called after each rough-draft phase (INTERFACE, PSEUDOCODE, SKELETON).

**Core principle:** Detect drift early before implementation diverges from design.

**Announce at start:** "I'm using the verify-phase skill to check alignment with the design document."

## When to Use

Use this skill when:
- Completing a rough-draft phase (INTERFACE, PSEUDOCODE, or SKELETON)
- You want to verify phase output matches the original design decisions
- Before transitioning between rough-draft phases

## When NOT to Use

Do NOT use this skill when:
- No design document exists yet (use `/brainstorming` first)
- In implementation phase (design is already finalized)
- No rough-draft output to verify

## Behavior

1. Read current phase output
2. Read design document
3. Use LLM to evaluate alignment
4. If aligned: proceed
5. If drift detected:
   - Present what changed, pros/cons, suggestion
   - Ask user: Accept (return to brainstorm), Reject (redo), or Partial
6. Handle user choice

## Implementation

Called by rough-draft skill after each phase with:
- `currentPhase`: INTERFACE | PSEUDOCODE | SKELETON
- `phaseOutput`: content produced

### Step 1: Get Design Document

Use the MCP tool to get the design document:

```
Tool: mcp__mermaid__get_document
Args: { "project": "<project-path>", "session": "<session-name>", "id": "design" }
```

Or read from filesystem:

```bash
cat .collab/<session-name>/documents/design.md
```

### Step 2: Construct Comparison Prompt

Build a prompt to evaluate alignment:

```
Compare the following {currentPhase} output against the design document.

Design Document:
{design_doc_content}

{currentPhase} Output:
{phaseOutput}

Questions:
1. Does this align with the design decisions?
2. Are there any additions not in the original design?
3. Are there any omissions from the design?

If aligned, respond: ALIGNED
If drift detected, respond with:
DRIFT DETECTED
What changed: [list