verification-gates

1# Verification Gates
2 
3You are implementing verification gates - explicit checkpoints where work is validated before proceeding. This prevents cascading errors and ensures quality at each phase.
4 
5## Core Principle
6 
7**Never proceed to the next phase with unverified assumptions from the previous phase.**
8 
9A verification gate is a deliberate pause to confirm that prerequisites are met before continuing.
10 
11## Standard Verification Gates
12 
13### Gate 1: Requirements Verification
14 
15Before starting design:
16 
17- [ ] All requirements are documented and clear
18- [ ] Ambiguities have been resolved with stakeholders
19- [ ] Non-requirements are explicitly stated
20- [ ] Acceptance criteria are defined
21- [ ] Edge cases are identified
22 
23**Actions:**
241. Review requirements document
252. Identify any unclear items
263. Get explicit confirmation on ambiguous points
274. Document answers
28 
29### Gate 2: Design Verification
30 
31Before starting implementation:
32 
33- [ ] Design addresses all requirements
34- [ ] Technical approach is validated
35- [ ] Interfaces are defined
36- [ ] Data model is complete
37- [ ] Error handling is planned
38- [ ] Design has been reviewed (self or peer)
39 
40**Actions:**
411. Walk through design against requirements
422. Review with rubber duck or teammate
433. Check for missing pieces
444. Get approval to proceed
45 
46### Gate 3: Implementation Verification
47 
48Before calling task complete:
49 
50- [ ] Code compiles/runs without errors
51- [ ] All tests pass
52- [ ] New code has test coverage
53…