Gate Check

Validate all gate criteria are met before advancing the PRD lifecycle version.

Workflow Overview

1. Load Gate Criteria → Read target gate requirements from PRD.md
2. Verify Evidence → Check required artifacts exist with valid IDs
3. Assess Readiness → Evaluate handoff requirements
4. Report → Pass/Block with specific gaps

Core Output Template

Gate Reference

Step 1: Load Gate Criteria

1. Read PRD.md gate section for target version
2. Extract all required criteria
3. Identify artifact types needed (BR, UJ, API, CFD)

Checklist

• Target gate identified
• All criteria extracted
• Required artifact types listed

Step 2: Verify Evidence

For each required criterion:

1. Check artifact exists in SoT/
2. Verify artifact status is not "Draft"
3. Confirm cross-references are valid
4. Check for required CFD-XXX evidence

Evidence Matrix

Checklist

• All required BR-XXX verified
• All required UJ-XXX verified
• All required API-XXX verified
• Evidence chain (CFD → BR) validated

Step 3: Assess Handoff Readiness

Check downstream requirements:

1. Next agent has context needed
2. No open blockers in current EPIC
3. Documentation is current

Checklist

• EPIC Session State section has no blockers
• README.md is synchronized
• Handoff documentation exists

Step 4: Generate Report

markdown
1## Gate Check Report: v0.X → v0.Y
2
3**Status**: [PASS / BLOCK]
4**Date**: YYYY-MM-DD
5
6### Criteria Assessment
7
8| Criterion | Status | Evidence |
9|-----------|--------|----------|
10| [Criterion 1] | ✅/❌ | [ID or gap] |
11| [Criterion 2] | ✅/❌ | [ID or gap] |
12
13### Missing Artifacts
14- [ ] [Specific gap with required action]
15
16### Recommendation
17[Proceed to v0.Y / Address [N] gaps before advancing]

Quality Gates

Pass Checklist

• All criteria evaluated (none skipped)
• Evidence is traceable to IDs
• Recommendation is actionable

Testability Check

• Report can be validated against PRD.md criteria
• Missing artifacts are specific and findable

Anti-Patterns

Boundaries

DO:

• Validate against documented criteria
• Identify specific gaps
• Provide actionable recommendations

DON'T:

• Create missing artifacts (just report)
• Override gate blocks
• Make subjective quality judgments

Handoff

After gate check:

• If PASS: Advance PRD version, trigger ghm-status-sync
• If BLOCK: Return to current stage, address gaps