# Spec Review Process

Detailed process for reviewing a spec-kit specification before moving to planning.

## 1. Locate the Spec

```bash
BRANCH=$(git branch --show-current)
SPEC_FILE="specs/${BRANCH}/spec.md"

if [[ ! -f "$SPEC_FILE" ]]; then
  echo "Error: $SPEC_FILE not found. Run /speckit.specify first." >&2
  return 1
fi
```

## 2. Run the Critique

```bash
orch consensus --mode critique --temperature 0.8 \
  --file "$SPEC_FILE" \
  "$(cat ~/.claude/skills/spec-review/prompts/spec-critique.txt)" \
  flash deepseek gpt
```

**Why these settings**:
- `--mode critique` - Models actively look for problems
- `--temperature 0.8` - Encourages finding edge cases
- Three diverse models catch different blind spots

## 3. Interpret Results

Look for:

**Consensus issues** (multiple models flagged):
- These are high-confidence problems
- Address before proceeding

**Single-model concerns**:
- May be false positives or edge cases
- Evaluate on merit

**Categories of issues**:
- Requirements clarity - ambiguous language
- Completeness - missing edge cases
- Scope - feature creep or unbounded
- Feasibility - contradictions, risks

## 4. Next Steps

| Result | Action |
|--------|--------|
| Blockers found | Fix spec, re-run review |
| Minor issues | Consider fixing, can proceed |
| Clean | Ready for `/speckit.plan` |
