validate

Mission Validate — Let Reality Speak

Every action is a hypothesis test. Validation is how reality answers.

Run acceptance criteria without advancing. Use to check your work, verify after a fix, or confirm the full mission is healthy. This is pure Observation — the most honest phase of the OODA cycle.

Target: $ARGUMENTS

---

Procedure

1. Read .mission/plan.md and .mission/progress.md.

2. Determine scope:

   • $ARGUMENTS is a number → validate that specific milestone
   • $ARGUMENTS is "all" → validate ALL milestones (full sweep)
   • $ARGUMENTS is empty → validate the current milestone (first incomplete)

3. For each milestone, run every acceptance criterion from the plan.

4. Report:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
VALIDATION: Milestone {N}: {title}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  ✅ `bun test` — passed (12 tests, 0 failures)
  ✅ `bun run build` — passed
  ❌ `bun run typecheck` — FAILED
     → src/api/users.ts:42 — Type 'string' not assignable to 'number'
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Result: 2/3 passed, 1 FAILED

1. For "all" validation, show a summary:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
FULL VALIDATION SWEEP
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  ✅ Milestone 1: Set up schema — all pass
  ✅ Milestone 2: API routes — all pass
  ❌ Milestone 3: Frontend — 1/3 failed
  ⬜ Milestone 4: Integration — not yet implemented
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

1. Suggest next action:
   • All pass → "Validation clean. Continue with /mission:continue."
   • Failures → "Mismatches detected. Fix the failures, then re-run /mission:validate."

Rules

• Run commands, don't inspect. Validation means executing commands, not reading code and deciding it "looks right." Self-assessment is the enemy of truth.
• Report precisely. Include exact error output. This is observation data for whoever acts on it next.
• Don't fix anything. This is observation, not action. Fixing happens in /mission:start or /mission:continue.