How do I install the Ghm Status Sync skill?

Run npx skillmds@latest add majiayu000/ghm-status-sync-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ghm Status Sync safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ghm Status Sync?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ghm Status Sync free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ghm Status Sync?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ghm Status Sync by majiayu000 — Agent Skill

Name: Ghm Status Sync
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

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.

majiayu000 Updated Sep 22, 2026 567 repo stars

File contents

Status Sync

Synchronize the README.md Command Center with the current project state after gate advancement or EPIC status changes.

Workflow Overview

Load Context → Read README.md, PRD.md metadata, Active EPIC Session State section
Extract State → Pull lifecycle stage, blockers, metrics
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:

README.md (current state)
PRD.md (metadata block for lifecycle stage)
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:

Lifecycle Stage: Update header to match PRD.md
Gate Table:
- 🟢 = Passed gates (all criteria met)
- 🟡 = Current gate (in progress)
- ⚪ = Future gates (not started)
Active EPIC: Update metadata in Active Work section
Blockers: Sync from EPIC Session State section
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

---name: ghm-status-sync-2description: 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 SyncSynchronize the README.md Command Center with the current project state after gate advancement or EPIC status changes.## Workflow Overview1. **Load Context** → Read README.md, PRD.md metadata, Active EPIC Session State section2. **Extract State** → Pull lifecycle stage, blockers, metrics3. **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 ContextRead 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 StatePull 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 DashboardApply synchronization rules:1. **Lifecycle Stage**: Update header to match PRD.md2. **Gate Table**: - 🟢 = Passed gates (all criteria met) - 🟡 = Current gate (in progress) - ⚪ = Future gates (not started)3. **Active EPIC**: Update metadata in Active Work section4. **Blockers**: Sync from EPIC Session State section5. **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)## HandoffAfter status sync completes:- README.md is current and accurate- Ready for next work session- Gate-check skill can validate if advancing

Frequently asked questions