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.

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 Section 0
2. Extract State → Pull lifecycle stage, blockers, metrics
3. Update Dashboard → Sync README sections with current truth

Core Output Template

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 Section 0 (blockers, progress)

Checklist

• README.md loaded
• PRD.md metadata extracted
• Active EPIC identified and Section 0 read

Step 2: Extract Current State

Pull authoritative values:

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 Section 0

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

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