Orient {
  Read `VISION.md` from the repo root. This is your compass.
  Read `CLAUDE.md` for coding standards, architecture, and testing rules.
  Run `git log --oneline -30` to see recent progress.
  Scan the codebase structure to understand current state.
}

Assess {
  Compare current state against the vision.
  What's broken? What's missing? What's partial? What's built but drifted from the vision?
  What has weak test coverage? What violates CLAUDE.md conventions?
  What's ugly, slow, or confusing?
}

Prioritize {
  Pick the single highest-impact next action. Priority order:
  1. **Broken** — Failing tests, lint errors, runtime bugs. Fix before anything else.
  2. **Missing** — Features described in the vision that don't exist yet.
  3. **Partial** — Implementations that are started but incomplete.
  4. **Undertested** — Code missing test layers per CLAUDE.md TestCoverage rules.
  5. **Misaligned** — Code that works but doesn't follow CLAUDE.md patterns or architecture.
  6. **Polish** — Performance, accessibility, UX, documentation, naming.

  If the user provided a focus via $ARGUMENTS, weight it heavily but don't ignore broken things.
}

Plan {
  State what you're about to do and why, in one sentence.
  Break it into small tasks (<50 lines each).
  If the work touches multiple layers (domain, infrastructure, application, routes), plan the test layers you'll need.
}

Build {
  Follow TDD. Red-Green-Refactor. No exceptions.
  Use the right combination of test layers for the type of change (see CLAUDE.md TestCoverage).
  Run tests before and after every change. If tests fail, fix them before moving on.
  Don't break what works.
}

Commit {
  Conventional commit after each meaningful unit of work.
  Small commits, continuous progress. Don't batch large changes.
}

Repeat -> Go back to Orient. The codebase has changed — reassess.