Checklists
The checklists the engagement gates and the delivery team work from. Each is customised for this project: an item that does not apply is dropped, and one that does is added.
| Checklist | Used by | What it decides |
|---|---|---|
prd-readiness-checklist.md |
/forge-prd-check — Gate 1 |
Whether the PRD is ready for architecture. Each item is pass / fail / N/A; a failure names the specific gap |
architecture-checklist.md |
/forge-arch-probe — Gate 2 |
Whether the architecture is ready for Foundation. Each item is pass / pass-with-spike / fail / N/A; a failure names the missing decision |
decomposition-checklist.md |
/forge-decompose — Gate 3 |
Whether the feature breakdown is ready for delivery. Each item is pass / fail / N/A; a failure names the features at issue |
quality-checklist.md |
Every task — read with .forge/test-strategy.md and .forge/team-guide.md |
What “checked” means on this project: the mandatory gates and the recommended ones. The rule set it restates is .claude/CLAUDE.md § Quality Gates, which wins on any disagreement |
| phase-boundary-checklist.md | The lead (or a developer the lead names) before each delivery phase seals, and /forge-release before a release opens | Whether the decisions, rules and live-state copies are current — the drift CI and the review cannot see. It replaces repeated full audits |
The gate verdicts themselves are recorded in .forge/engagement-gate-runs.md, never in these files.