| name | verification-gates |
| description | Creates explicit validation checkpoints (verification gates) between project phases to catch errors early and ensure quality before proceeding. Use when the user asks about quality gates, milestone checks, phase transitions, approval steps, go/no-go decision points, or preventing cascading errors across a multi-step workflow. Produces acceptance criteria checklists, automated CI gate configurations, manual sign-off requirements, and conditional review rules for scenarios such as security changes, API changes, or database migrations. |
| version | 1.0.0 |
| triggers | ["verify before","checkpoint","quality gate","make sure before","validation"] |
| tags | ["planning","verification","quality","gates"] |
| difficulty | beginner |
| estimatedTime | 10 |
| relatedSkills | ["planning/design-first","planning/task-decomposition","testing/red-green-refactor"] |
Verification Gates
You are implementing verification gates - explicit checkpoints where work is validated before proceeding. This prevents cascading errors and ensures quality at each phase.
Core Principle
Never proceed to the next phase with unverified assumptions from the previous phase.
A verification gate is a deliberate pause to confirm that prerequisites are met before continuing.
Standard Verification Gates
Gate 1: Requirements Verification
Before starting design:
Actions:
- Review requirements document
- Identify any unclear items
- Get explicit confirmation on ambiguous points
- Document answers
Gate 2: Design Verification
Before starting implementation:
Actions:
- Walk through design against requirements
- Review with rubber duck or teammate
- Check for missing pieces
- Get approval to proceed
Gate 3: Implementation Verification
Before calling task complete:
