Stage-Gate Checklist: [project name]
One row per gate. A gate is passed on evidence, decided by you, and recorded here with a date. "Pass with actions" means proceed, with the listed findings accepted onto the plan. Filled in across Sessions 5–8.
| Gate | Run via | Entry criteria | Evidence reviewed | Decision (pass / pass with actions / fail) | Actions accepted | Signed / date |
|---|---|---|---|---|---|---|
| Business (CEO) | /plan-ceo-review |
Spec committed | The spec | |||
| Engineering | /plan-eng-review |
Spec committed | The spec + your marked-up review | |||
| Design | /plan-design-review |
Spec committed | The spec | |||
| Developer experience | /plan-devex-review |
Spec committed | The spec | |||
| Test | /ios-qa full pass + web /qa-only |
Build complete, all platforms, all stages | QA reports (device + web) + cross-platform smoke test + /ios-design-review |
|||
| Security | /cso |
Test gate passed | CSO report |
Baseline record
- Plan baselined (commit labelled
plan-baseline): _________ (date) - Included in baseline: spec · gate sign-offs 1–4 · design system · diagram · three platform roadmaps
- Sequencing decision (which platform, which session, why): _________
Exceptions log
Every time the fence moved (/unfreeze → change → /freeze), one line:
what, why, when. An empty log on a real project means nobody was looking.
| Date | What changed outside the plan | Why | Fence restored? |
|---|---|---|---|
Closure
- [ ] Shipped (
/ship) - [ ] Scaffolding removed (
/ios-clean) - [ ] Handover pack produced (
/document-generate→/make-pdf) - [ ] Lessons banked (
/retro→/learn)