Skip to content

mattgierhart/PRD-driven-context-engineering / .claude/skills/ghm-status-sync

ghm-status-sync

Verified

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 Session State section
  2. Extract State β†’ Pull lifecycle stage, blockers, metrics
  3. Update Dashboard β†’ Sync README sections with current truth

Core Output Template

ElementDefinitionEvidence
Lifecycle StageCurrent PRD version from PRD.mdCurrent Lifecycle Gate: v0.X
Gate StatusVisual progress indicators🟒 Complete / 🟑 In Progress / βšͺ Pending
Active EPICCurrent work from EPIC headerEPIC-XX: Title
BlockersOpen blockers from EPIC Session State sectionList 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:

FieldSource
Lifecycle StagePRD.md Current Lifecycle Gate
Gate ProgressPRD.md gate table
Active EPICREADME.md Active Work section
BlockersEPIC Session State section
MetricsREADME.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

PatternExampleFix
Stale gate status🟒 on gate with missing criteriaβ†’ Verify all criteria before marking complete
Missing blockersEPIC has blockers, README shows none→ Always sync from EPIC Session State section
Wrong EPIC referenceREADME 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
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 466kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product β€” it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product β€” not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial β€” a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK β€” model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER β€” read BEFORE opening the target file; don't skip because it "looks like a one-liner" β€” whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) β€” never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named β€” don't Read the file).Stars: 196kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 196kUpdated Claude CodeCodexVerifiedInstall