/ghm-status-sync
Synchronizes README.md Command Center with current project state. Triggers on gate changes, EPIC status changes, or explicit `/ghm-status-sync` invocation. Outputs updated README.md dashboard with current lifecycle stage, blockers, and metrics.
$ npx -y skills add mattgierhart/PRD-driven-context-engineering --skill ghm-status-sync --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/ghm-status-sync
Context preview
The summary Claude sees to decide when to auto-load this skill.
Synchronizes README.md Command Center with current project state. Triggers on gate changes, EPIC status changes, or explicit `/ghm-status-sync` invocation. Outputs updated README.md dashboard with current lifecycle stage, blockers, and metrics.
SKILL.md
ghm-status-sync.SKILL.mdname: ghm-status-sync
description: >
Synchronizes README.md Command Center with current project state.
Triggers on gate changes, EPIC status changes, or explicit `/ghm-status-sync` invocation.
Outputs updated README.md dashboard with current lifecycle stage, blockers, and metrics.
context: inline
allowed-tools:
- Read
- Write
- Edit
- Glob
- Grep
Status Sync
Synchronize the README.md Command Center with the current project state after gate advancement or EPIC status changes.
Workflow Overview
1. **Load Context** → Read README.md, PRD.md metadata, Active EPIC Session State section 2. **Extract State** → Pull lifecycle stage, blockers, metrics 3. **Update Dashboard** → Sync README sections with current truth
Core Output Template
| Element | Definition | Evidence | |---------|------------|----------| | **Lifecycle Stage** | Current PRD version from PRD.md | `Current Lifecycle Gate: v0.X` | | **Gate Status** | Visual progress indicators | 🟢 Complete / 🟡 In Progress / ⚪ Pending | | **Active EPIC** | Current work from EPIC header | `EPIC-XX: Title` | | **Blockers** | Open blockers from EPIC Session State section | List with severity |
Step 1: Load Context
Read these files in order: 1. `README.md` (current state) 2. `PRD.md` (metadata block for lifecycle stage) 3. Active EPIC Session State section (blockers, progress)
Checklist
- [ ] README.md loaded
- [ ] PRD.md metadata extracted
- [ ] Active EPIC identified and Session State section read
Step 2: Extract Current State
Pull authoritative values:
| Field | Source | |-------|--------| | Lifecycle Stage | PRD.md `Current Lifecycle Gate` | | Gate Progress | PRD.md gate table | | Active EPIC | README.md `Active Work` section | | Blockers | EPIC Session State section | | Metrics | README.md Truth Table |
Step 3: Update README Dashboard
Apply synchronization rules:
1. **Lifecycle Stage**: Update header to match PRD.md 2. **Gate Table**:
- 🟢 = Passed gates (all criteria met)
- 🟡 = Current gate (in progress)
- ⚪ = Future gates (not started)
3. **Active EPIC**: Update metadata in Active Work section 4. **Blockers**: Sync from EPIC Session State section 5. **Squad Status** (Section: `squad-status`): Update agent and EPIC tables:
- For each agent in `.claude/agents/`: check MEMORY.md mtime for "Last Active", grep EPICs for agent name for "Current EPIC"
- For each EPIC in `epics/`: read State field, Epic Lead, and Change Log last date
- Status values: `active` (session <2h old), `idle` (no recent activity), `blocked` (blocker in session state)
Quality Gates
Pass Checklist
- [ ] README lifecycle stage matches PRD.md
- [ ] Gate indicators are accurate (no 🟢 on incomplete gates)
- [ ] Active EPIC reference is current
- [ ] Blockers reflect actual state
Testability Check
- [ ] Can be validated by comparing README to PRD.md
- [ ] Gate status is traceable to gate criteria
Anti-Patterns
| Pattern | Example | Fix | |---------|---------|-----| | Stale gate status | 🟢 on gate with missing criteria | → Verify all criteria before marking complete | | Missing blockers | EPIC has blockers, README shows none | → Always sync from EPIC Session State section | | Wrong EPIC reference | README points to closed EPIC | → Check EPIC status before updating |
Boundaries
**DO**:
- Status synchronization
- Link updates
- Gate progression indicators
**DON'T**:
- Content changes to descriptions
- Create new sections
- Modify PRD.md (read-only source)
Handoff
After status sync completes:
- README.md is current and accurate
- Ready for next work session
- Gate-check skill can validate if advancing
Read more
name: ghm-status-sync description: > Synchronizes README.md Command Center with current project state. Triggers on gate changes, EPIC status changes, or explicit `/ghm-status-sync` invocation. Outputs updated README.md dashboard with current lifecycle stage, blockers, and metrics. context: inline allowed-tools: - Read - Write - Edit - Glob - Grep
Status Sync
Synchronize the README.md Command Center with the current project state after gate advancement or EPIC status changes.
Workflow Overview
1. **Load Context** → Read README.md, PRD.md metadata, Active EPIC Session State section 2. **Extract State** → Pull lifecycle stage, blockers, metrics 3. **Update Dashboard** → Sync README sections with current truth
Core Output Template
| Element | Definition | Evidence | |---------|------------|----------| | **Lifecycle Stage** | Current PRD version from PRD.md | `Current Lifecycle Gate: v0.X` | | **Gate Status** | Visual progress indicators | 🟢 Complete / 🟡 In Progress / ⚪ Pending | | **Active EPIC** | Current work from EPIC header | `EPIC-XX: Title` | | **Blockers** | Open blockers from EPIC Session State section | List with severity |
Step 1: Load Context
Read these files in order: 1. `README.md` (current state) 2. `PRD.md` (metadata block for lifecycle stage) 3. Active EPIC Session State section (blockers, progress)
Checklist
- [ ] README.md loaded
- [ ] PRD.md metadata extracted
- [ ] Active EPIC identified and Session State section read
Step 2: Extract Current State
Pull authoritative values:
| Field | Source | |-------|--------| | Lifecycle Stage | PRD.md `Current Lifecycle Gate` | | Gate Progress | PRD.md gate table | | Active EPIC | README.md `Active Work` section | | Blockers | EPIC Session State section | | Metrics | README.md Truth Table |
Step 3: Update README Dashboard
Apply synchronization rules:
1. **Lifecycle Stage**: Update header to match PRD.md 2. **Gate Table**:
- 🟢 = Passed gates (all criteria met)
- 🟡 = Current gate (in progress)
- ⚪ = Future gates (not started)
3. **Active EPIC**: Update metadata in Active Work section 4. **Blockers**: Sync from EPIC Session State section 5. **Squad Status** (Section: `squad-status`): Update agent and EPIC tables:
- For each agent in `.claude/agents/`: check MEMORY.md mtime for "Last Active", grep EPICs for agent name for "Current EPIC"
- For each EPIC in `epics/`: read State field, Epic Lead, and Change Log last date
- Status values: `active` (session <2h old), `idle` (no recent activity), `blocked` (blocker in session state)
Quality Gates
Pass Checklist
- [ ] README lifecycle stage matches PRD.md
- [ ] Gate indicators are accurate (no 🟢 on incomplete gates)
- [ ] Active EPIC reference is current
- [ ] Blockers reflect actual state
Testability Check
- [ ] Can be validated by comparing README to PRD.md
- [ ] Gate status is traceable to gate criteria
Anti-Patterns
| Pattern | Example | Fix | |---------|---------|-----| | Stale gate status | 🟢 on gate with missing criteria | → Verify all criteria before marking complete | | Missing blockers | EPIC has blockers, README shows none | → Always sync from EPIC Session State section | | Wrong EPIC reference | README points to closed EPIC | → Check EPIC status before updating |
Boundaries
**DO**:
- Status synchronization
- Link updates
- Gate progression indicators
**DON'T**:
- Content changes to descriptions
- Create new sections
- Modify PRD.md (read-only source)
Handoff
After status sync completes:
- README.md is current and accurate
- Ready for next work session
- Gate-check skill can validate if advancing
PRD-driven Context Engineering: A systematic approach to building AI-powered products using progressive documentation and context-aware development workflows
Repo: mattgierhart/PRD-driven-context-engineering
Other skills on prd-driven-context-engineering.
- /SKILL_TEMPLATE
[1-2 sentence description of what this skill does]. Triggers on [specific phrases/contexts that should activate this skill]. Outputs [what the skill produces].
Open skill - /ghm-gate-check
Validates gate criteria before PRD lifecycle advancement by delegating to the readiness scoring pipeline (scripts/readiness.py). Returns a graduated PASS / WARN / BLOCK verdict with top blockers and their causal chain. Triggers before advancing from v0.X to v0.Y or explicit
Open skill - /ghm-harvest
Extracts durable insights from temp/ files to SoT during EPIC Phase E. Triggers at EPIC completion or explicit `/ghm-harvest` invocation. Outputs new SoT entries and archive manifest.
Open skill - /ghm-id-register
Validates and registers new SoT IDs with cross-reference integrity. Triggers when creating BR-XXX, UJ-XXX, API-XXX, or CFD-XXX entries. Outputs formatted SoT entry with validated cross-references.
Open skill - /ghm-self-install
Install the PRD-Driven Context Engineering methodology into a fresh OR existing repository — the subscription-native alternative to forking the whole repo. Runs an interactive wizard that seeds the framework (.claude/ hooks, skills, agents, rules, scripts) without clobbering
Open skill - /ghm-sot-builder
Creates new Source of Truth (SoT) files when existing templates don't fit your needs. Triggers on requests to create a new SoT file, add a new artifact type, or when user says "I need to track [X] but there's no SoT for it", "create SoT", "new source of truth". Outputs a
Open skill

