Phase 5 — Quality & Planning
Quality Gate Specification
The automated checks that catch what code review misses
2 min read · Document 19 of 30
What is this document?
The Quality Gate Specification lists the checks every change must pass — lint, type checks, tests, accessibility, performance budgets, security scans — and the threshold for each.
Gates block merges and releases automatically, so quality does not depend on memory.
Why does it matter?
- Without defined gates, “done” means “it ran on my machine”.
- Thresholds make quality measurable and comparable over time.
- Failures are caught minutes after they are introduced, not weeks later.
What's inside?
- Gates — Each check, its tool and its threshold.
- Pipeline placement — Which gates run on commit, merge and release.
- Exceptions — Who may waive a gate and how it is recorded.
LintType checkUnit testsIntegrationAccessibilitySecurity
How CREAH generates it
CREAH builds this document from your Stage 0 answers and interview. Questions that shape it include:
- What is an acceptable page load budget?
- Which security scans are required?
- Who can approve a release?
Example excerpt
## Gate 4 — Accessibility
Tool: automated audit on every page in CI
Threshold: 0 critical violations, score ≥ 95
Blocks: merge to main
## Gate 6 — Security
Dependency scan + secret scan on every commit; any high finding blocks release.