# Plan Review Process

Detailed process for evaluating architecture and technology decisions before implementation.

## 1. Locate the Files

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

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

## 2. Run Devil's Advocate Review

```bash
orch consensus --mode open --temperature 1.0 \
  --file "$PLAN_FILE" \
  --file "$SPEC_FILE" \
  "$(cat ~/.claude/skills/spec-review/prompts/plan-review.txt)" \
  flash:for deepseek:against gpt:neutral
```

**Why these settings**:
- `--mode open` - Freeform responses, not structured verdicts
- `--temperature 1.0` - Maximum divergent thinking
- **Stances**:
  - `:for` - Argues in favor of the plan
  - `:against` - Actively looks for problems
  - `:neutral` - Balanced assessment

## 3. Interpret the Stances

**From the :for model**:
- What's good about this approach
- Why the choices make sense
- Strengths to preserve

**From the :against model** (most valuable):
- Risks and concerns
- Alternative approaches
- What could go wrong
- Hidden complexity

**From the :neutral model**:
- Balanced tradeoff assessment
- Overall recommendation
- Key decision points

## 4. Synthesize

- Where models agree → high confidence
- Where models disagree → needs decision
- :against concerns that :for can't rebut → real issues

## 5. Next Steps

| Result | Action |
|--------|--------|
| Significant concerns | Revise plan |
| Minor risks noted | Document risks, proceed |
| Clean | Ready for `/speckit.tasks` |
