ghm-status-sync

Synchronize README Command Center dashboard sections with current project state.

193|9|Updated Jul 10, 2025
One-click install
npx skills add https://github.com/mattgierhart/PRD-driven-context-engineering --skill ghm-status-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ghm-status-sync
Source: https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/ghm-status-sync
Command: npx skills add https://github.com/mattgierhart/PRD-driven-context-engineering --skill ghm-status-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Keeps README Command Center aligned with the live state of projects by updating lifecycle stages, blockers, and EPIC status automatically after changes.

Core Features & Use Cases

  • Automatically refreshes the Command Center to reflect gate progress and EPIC changes.
  • Aggregates blockers and metrics into a single, actionable dashboard.
  • Use Case: After a gate update, invoke the skill to ensure the dashboard mirrors current truth.

Quick Start

Run ghm-status-sync after a gate or EPIC status change to refresh the dashboard.

Frequently Asked Questions about ghm-status-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update my README dashboard after project gate advancements?

To update your README dashboard after gate advancements, synchronize the Command Center by reading PRD.md metadata and writing the updated lifecycle stages and metrics to README.md.

What is the best way to keep EPIC tracking metadata in sync with my project dashboard?

Keeping EPIC tracking metadata in sync involves extracting authoritative state from PRD.md and refreshing the README dashboard sections to accurately reflect current blockers and status changes.

When should I refresh my project dashboard for accurate epic tracking?

You should refresh your project dashboard for accurate epic tracking immediately after EPIC status changes or gate advancements to ensure the dashboard mirrors the current project truth.

Does this status sync approach require specific files to update the dashboard?

Yes, this status sync approach requires existing README.md and PRD.md files to extract authoritative project state and write the updated dashboard sections accordingly.

Can I automate README dashboard updates when blockers change?

You can automate README dashboard updates by invoking the synchronization command after blockers change, which aggregates metrics and refreshes the dashboard sections automatically.

Why does my project dashboard show outdated lifecycle stages after a gate update?

Your project dashboard shows outdated lifecycle stages because it has not been synchronized since the gate update, requiring a refresh to extract the latest state from PRD.md.