This repository runs a strict team workflow. The order is fixed:
PLAN → BUILD → CODE REVIEW → FLOW REVIEW → GREEN → COMMIT → PR
- No code without an approved plan. Every task starts with the
plannerskill (team leader, Fable). Plans live in.claude/workflow/plans/and must readSTATUS: APPROVEDbefore implementation begins. - Implementation follows the
developerskill. Tasks are delegated by the plan's weight column: Heavy → lead, Medium → dev-sonnet, Light → dev-haiku. - No
git commituntil the/reviewerskill (Opus, adversarial) has writtenVERDICT: GREENin BOTH.claude/workflow/reviews/latest-code.mdand.claude/workflow/reviews/latest-flow.mdfor the current change set. - No PR until a flow review (Playwright or Claude in Chrome, actually executed against the running app) passed on the final state being pushed. Any change after the last flow review makes it stale — re-run it.
- RED verdict → fix every BLOCKER and MAJOR → full re-review. Findings are never argued away or self-downgraded; only the reviewer withdraws a finding.
- Scope changes mid-build go back through
plannerfor re-approval first.
The goal: strict reviews, high-grade code quality, an architecture that survives adversarial testing. When in doubt, the stricter interpretation wins.