Analyze

Cross-artifact consistency check. Catch drift before it becomes code.

Process

1. Read the spec (specs/active/<id>-<slug>.md).
2. Read the plan (plans/active/<id>-<slug>.md).
3. Read the tasks in tasks/TASKS.md filtered by spec:<id>.
4. Run the consistency checklist (below).
5. Report findings, severity-tagged.
6. Write the machine marker (e2e-audit spec-pipeline-1 — this is what makes the gate real; without it next-task.sh/workflow-state.sh see the spec as unanalyzed): Write .claude/state/analyze-<id>.json with exactly:

   {"verdict": "PASS|BLOCK", "blockers": ["<each BLOCKER finding>"], "date": "<ISO>"}

   <id> is the numeric spec id (e.g. analyze-042.json). Re-running /analyze overwrites the marker — verdict reflects the LATEST run.
7. Block /implement if any blockers — the marker's verdict: BLOCK is enforced by next-task.sh --require-analyze (loop path), not just by this prose.

Consistency checks

• Every spec acceptance criterion has at least one task that exercises it.
• Every plan component is implemented by at least one task.
• No task references a file outside the plan's scope.
• No cyclic dependencies in the task DAG.
• Every task's accept: command is syntactically valid (no obvious typos).
• All declared dependencies (packages, services, MCP servers) appear in install/setup tasks.
• Spec, plan, and tasks share the same id namespace.
• No open [OQ] items in the spec.
• Phase boundaries align — every plan phase has tasks; no orphan tasks.
• Risks in the plan have mitigation tasks or explicit acceptance of the risk.
• Backwards-compat constraints from the spec appear as tests.

Output

# Analysis — feature <id> — <date>

## Coverage
- Spec criteria with tasks: 8/8 ✓
- Plan components with tasks: 6/6 ✓
- Tasks with accept commands: 12/12 ✓

## Gaps
- BLOCKER: Acceptance criterion "rate limit 100 req/min" has no task.
- HIGH: Plan mentions `redis-rate-limiter` but no install task.

## Cycles
- None ✓

## Verdict
BLOCK — 1 blocker, 1 high. Address before /implement.

After save: post the summary to the user. If green, "Ready for /implement." If red, list the gaps.