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.

FileKindSize
SKILL.mdskill md3.6 KB
assets/status-sync-template.mdmarkdown3.9 KB
references/examples.mdmarkdown6.4 KB
references/sync-triggers.mdmarkdown3.7 KB

references/sync-triggers.md

View on GitHub
# Status Sync Triggers

**Purpose**: When to update README Command Center status.

---

## Automatic Triggers (Must Sync)

### Trigger 1: Gate Status Change

**When**: Passing or blocking any PRD lifecycle gate

**Update**:
- Gate status (passed/blocked/conditional)
- Current PRD version
- Blockers (if blocked)
- Next milestone

**Frequency**: Immediately after gate check

---

### Trigger 2: EPIC Status Change

**When**: EPIC starts, completes, or gets blocked

**Update**:
- Active EPIC
- Progress percentage
- Blockers (if any)
- Timeline adjustment

**Frequency**: When EPIC state changes

---

### Trigger 3: Critical Blocker

**When**: P0/P1 blocker emerges that delays gate or launch

**Update**:
- Blocker list
- Overall health (change to πŸ”΄ Blocked)
- Timeline impact
- Mitigation plan

**Frequency**: Immediately when blocker identified

---

### Trigger 4: Launch Metrics Change

**When**: Post-launch, metrics significantly change

**Update**:
- Metrics dashboard
- Health status (if metrics below target)
- Action items

**Frequency**: Daily (first week), weekly (after)

**Significant Change**: >10% deviation from target

---

## Scheduled Triggers (Should Sync)

### Trigger 5: Weekly Sync

**When**: Every Monday 9 AM (or weekly team sync)

**Update**:
- Progress indicators
- ID creation activity
- Recent changes
- Upcoming milestones

**Frequency**: Weekly

---

### Trigger 6: End of Sprint

**When**: Sprint retrospective or planning

**Update**:
- Completed work
- Sprint metrics
- Next sprint plan
- Team notes (what's going well, what needs attention)

**Frequency**: Bi-weekly (or sprint cadence)

---

### Trigger 7: Monthly Review

**When**: First Monday of month

**Update**:
- Full status review
- Metrics trends (vs last month)
- Roadmap adjustments
- Stakeholder communication

**Frequency**: Monthly

---

## Optional Triggers (Good to Sync)

### Trigger 8: Major Decision

**When**: Product/technical decision with PRD impact

**Update**:
- Team notes (decisions made)
- Impact on timeline or scope

**Example Decisions**:
- Pricing change
- Scope cut
- Architecture change

---

### Trigger 9: Team Change

**When**: Team member joins/leaves, ownership changes

**Update**:
- EPIC ownership
- Blocker ownership
- Contact information

---

### Trigger 10: External Dependency

**When**: Waiting on external team/vendor

**Update**:
- Blocker list (external dependency)
- Timeline impact
- Alternative plan (if dependency delays)

---

## Sync Frequency by Phase

| PRD Phase | Sync Frequency | Reason |
|-----------|----------------|--------|
| **v0.1-v0.3** (Planning) | Weekly | High decision rate |
| **v0.4-v0.6** (Design) | Bi-weekly | Steady progress |
| **v0.7** (Build) | Weekly | Active development |
| **v0.8** (Deployment) | Daily | Critical phase |
| **v0.9-v1.0** (Launch) | Daily (first week), then weekly | Metrics monitoring |

---

## Sync Checklist

Before syncing:

- [ ] Collect latest data (gate status, EPIC progress, metrics)
- [ ] Identify changes since last update
- [ ] Update dashboard numbers
- [ ] Flag blockers/risks
- [ ] Review team notes

During sync:

- [ ] Update Current Status section
- [ ] Update Progress Indicators
- [ ] Update Blockers & Risks
- [ ] Update Metrics (if applicable)
- [ ] Update Recent Changes
- [ ] Update Team Notes

After sync:

- [ ] Commit changes to README.md
- [ ] Notify team (Slack/email if major change)
- [ ] Schedule next sync

---

## Red Flags (Sync Immediately)

🚨 **Immediate Sync Needed**:
- Gate blocked (can't advance)
- Launch metrics 50%+ below target
- P0 bug in production
- Team member departure (blocking progress)
- External dependency delayed >1 week

---

*Reference: Use these triggers to determine when to sync status in `ghm-status-sync` skill.*
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: 471kUpdated 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: 198kUpdated 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: 198kUpdated 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: 198kUpdated Claude CodeCodexVerifiedInstall