Back to list
mattgierhart

ghm-gate-check

by mattgierhart

PRD-driven Context Engineering: A systematic approach to building AI-powered products using progressive documentation and context-aware development workflows

9🍴 2📅 Jan 24, 2026

SKILL.md


name: ghm-gate-check description: > Validates gate criteria before PRD lifecycle advancement. Triggers before advancing from v0.X to v0.Y or explicit /ghm-gate-check invocation. Outputs pass/block summary with missing artifacts list.

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

ElementDefinitionEvidence
Target GateVersion being validatedv0.3 → v0.4
StatusPass or BlockClear determination
Missing ArtifactsWhat's not completeSpecific list with IDs
RecommendationAction to takeProceed / Address gaps

Gate Reference

GateFocusKey Artifacts
v0.1 → v0.2Problem validatedCFD-XXX evidence
v0.2 → v0.3Market definedSegment definitions
v0.3 → v0.4Commercial viableBR-XXX, pricing
v0.4 → v0.5Journeys mappedUJ-XXX complete
v0.5 → v0.6Risks addressedRisk register
v0.6 → v0.7Architecture setAPI-XXX, schemas
v0.7 → v0.8Build completeTests passing
v0.8 → v0.9DeployedLive environment
v0.9 → v1.0LaunchedMetrics tracking

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

Criterion TypeVerification
Business RuleBR-XXX exists, status Active
User JourneyUJ-XXX exists, all steps defined
API ContractAPI-XXX exists, endpoints specified
Customer EvidenceCFD-XXX linked to BR-XXX

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 Section 0 has no blockers
  • README.md is synchronized
  • Handoff documentation exists

Step 4: Generate Report

## Gate Check Report: v0.X → v0.Y

**Status**: [PASS / BLOCK]
**Date**: YYYY-MM-DD

### Criteria Assessment

| Criterion | Status | Evidence |
|-----------|--------|----------|
| [Criterion 1] | ✅/❌ | [ID or gap] |
| [Criterion 2] | ✅/❌ | [ID or gap] |

### Missing Artifacts
- [ ] [Specific gap with required action]

### Recommendation
[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

PatternExampleFix
Skipping criteria"Probably fine"→ Verify each explicitly
Vague gaps"Needs more work"→ Cite specific missing ID
Override blocksAdvancing despite fails→ Address gaps first

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

Score

Total Score

75/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

+10
人気

GitHub Stars 100以上

0/15
最近の活動

1ヶ月以内に更新

+10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

+5

Reviews

💬

Reviews coming soon