Agent skill

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.

View SKILL.md on GitHub Repository
Stars 26
Forks 6

Install this agent skill to your Project

npx add-skill https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/ghm-status-sync

SKILL.md

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

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

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

mattgierhart/PRD-driven-context-engineering

prd-v05-technical-stack-selection

Make technology decisions for every product capability by discovering existing assets, evaluating vendor-aligned options, and categorizing as Reuse/Extend/Build/Buy/Integrate/Research during PRD v0.5 Red Team Review. Handles both greenfield and brownfield contexts. Triggers on "tech stack", "build or buy?", "what technologies?", "technical decisions", "what do we reuse?", "existing stack", "vendor constraint", "IBM-first", "what tools do we need?", "evaluate solutions", "select tech stack". Consumes FEA- (features), SCR- (screens), RISK- (constraints). Outputs TECH- entries with decisions, rationale, and cross-references. Feeds v0.6 Architecture Design.

26 6
Explore
mattgierhart/PRD-driven-context-engineering

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.

26 6
Explore
mattgierhart/PRD-driven-context-engineering

prd-v02-product-type-classification

Classify product approach into one of six types (Clone, Unbundle, Undercut, Slice, Wrapper, Innovation) based on competitive landscape. Triggers on PRD v0.2 work after competitive analysis, or when user asks "what type of product should we build?", "should we clone or innovate?", "is this a fast-follow opportunity?", "how should we position against competitors?", "clone vs undercut", "unbundle vs slice", or requests help choosing product strategy. Outputs BR- entries for product type classification and inherited GTM constraints.

26 6
Explore
mattgierhart/PRD-driven-context-engineering

prd-v03-outcome-definition

Define measurable success metrics (KPIs) tied to product type during PRD v0.3 Commercial Model. Triggers on requests to define success metrics, set KPI targets, determine what to measure, establish go/no-go thresholds, or when user asks "how do we measure success?", "what metrics matter?", "what's our target?", "how do we know if this works?", "define KPIs", "success criteria". Consumes Product Type Classification (BR-) from v0.2. Outputs KPI- entries with thresholds, evidence sources, and downstream gate linkages.

26 6
Explore
mattgierhart/PRD-driven-context-engineering

prd-v05-risk-discovery-interview

Surface risks through guided questioning, helping users consider pivots, constraints, and prioritization during PRD v0.5 Red Team Review. Triggers on requests to identify risks, stress-test the idea, perform red team review, or when user asks "what could go wrong?", "identify risks", "red team", "risk assessment", "challenge assumptions", "stress test the idea". Consumes all prior IDs (CFD-, BR-, FEA-, PER-, UJ-, SCR-) as interview context. Outputs RISK- entries with owner decisions and mitigations. Feeds v0.5 Technical Stack Selection.

26 6
Explore
mattgierhart/PRD-driven-context-engineering

ghm-gate-check

Validates gate criteria before PRD lifecycle advancement. Triggers before advancing from v0.X to v0.Y or explicit `/ghm-gate-check` invocation. Outputs pass/block summary with missing artifacts list.

26 6
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results