mattgierhart/ghm-status-sync
.claude/skills/ghm-status-sync/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add mattgierhart/PRD-driven-context-engineering ghm-status-syncInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 11:14 AM7.9s4 files scanned
SKILL.md
- name:
- ghm-status-sync
- description:
- >
- context:
- inline
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)
- For each agent in
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
Related Skills
mattgierhart/prd-v05-technical-stack-selection
tools
VerifiedTrustedCommunity
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.
28SKILL.mdUpdated Apr 16, 2026
mattgierhart/prd-v09-launch-metrics
development
VerifiedTrustedCommunity
Define success criteria and tracking setup for launch during PRD v0.9 Go-to-Market. Triggers on requests to define launch metrics, set up tracking, or when user asks "how do we measure launch success?", "launch KPIs", "tracking setup", "success criteria", "analytics", "launch goals". Outputs KPI- entries specialized for launch measurement.
28SKILL.mdUpdated Apr 16, 2026
mattgierhart/prd-v09-gtm-strategy
development
VerifiedTrustedCommunity
Define go-to-market strategy including launch plan, messaging, channels, and timing during PRD v0.9 Go-to-Market. Triggers on requests to plan launch, define GTM strategy, or when user asks "how do we launch?", "go-to-market", "launch plan", "marketing strategy", "messaging", "launch channels", "GTM". Outputs GTM- entries with launch plan components.
28SKILL.mdUpdated Apr 16, 2026
mattgierhart/prd-v09-feedback-loop-setup
development
VerifiedTrustedCommunity
Establish channels and processes for capturing and processing post-launch feedback during PRD v0.9 Go-to-Market. Triggers on requests to set up feedback systems, capture user input, or when user asks "how do we collect feedback?", "feedback loop", "user research", "post-launch feedback", "customer feedback", "NPS", "voice of customer". Outputs CFD- entries specialized for post-launch feedback capture.
28SKILL.mdUpdated Apr 16, 2026