Skip to main content

Approval Workflow

Every stage follows the same 3-step approval chain. The chain is sequential — the next step does not start until the current one passes.

① Claude Auto-Review → ② Human Approval (role-gated) → ③ Stage Locked → Unlocked

Step 1 — Claude Auto-Review​

  • Stage-specific enforcer agent runs (e.g. agent-s1-prd-enforcer)
  • Checks artifact against quality criteria from verify-s{n}.md
  • Auto-fixes issues using enhance-s{n}.md instructions
  • Only presents to human once APPROVED internally

Step 2 — Human Approval​

  • System checks logged-in role against designated approver — blocks if mismatch
  • For Stages 4 & 5: dual L1+L2 required (two separate named approvers)
  • Approver types their full name; role + timestamp recorded in session.md
  • Partial artifacts (from early EXIT) can be approved as TBD-gap versions

Step 3 — Post-Approval​

  • Stage marked complete in session.md
  • Next stage unlocked on Main Menu
  • Stage 3 only: stories uploaded to Jira via MCP
  • Main Menu re-displayed automatically after approval