メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Seed a fresh (greenfield) repository with the PRD-Driven Context Engineering scaffold — PRD.md, SoT/ knowledge files, EPIC templates, domain-profile config, and agent MEMORY starters. Invoked as /prd-ce:init when the plugin is installed. The framework itself (skills, agents, hooks, scripts) ships LIVE in the plugin; this skill only plants the consumer-owned files the plugin cannot carry as behavior. Triggers on "/prd-ce:init", "set up PRD lifecycle here", "scaffold a new PRD-CE project", "initialize the methodology". Outputs a seeded scaffold + a verification report.
Install the PRD-Driven Context Engineering methodology into a fresh OR existing repository — the subscription-native alternative to forking the whole repo. Runs an interactive wizard that seeds the framework (.claude/ hooks, skills, agents, rules, scripts) without clobbering product content. Triggers on "install the methodology", "adopt this into my repo", "self-install", "set up PRD lifecycle here", "onboard existing project". Outputs an installed framework + a verification report.
[1-2 sentence description of what this skill does]. Triggers on [specific phrases/contexts that should activate this skill]. Outputs [what the skill produces].
Define how system components connect, establishing boundaries, patterns, and integration approaches during PRD v0.6 Architecture. Triggers on requests to design architecture, create system design, define component relationships, or when user asks "design architecture", "system design", "how do components connect?", "architecture decisions", "technical architecture", "system overview". Consumes TECH- (stack selections), RISK- (constraints), FEA- (features). Outputs ARC- entries documenting architecture decisions with rationale. Feeds v0.6 Technical Specification.
Execute implementation within EPICs following test-first development, continuous SoT updates, and code traceability during PRD v0.7 Build Execution. Triggers on requests to start building, implement an epic, begin coding, or when user asks "start building", "implement epic", "coding", "development", "build execution", "implementation", "write code". Consumes EPIC- (context), TEST- (acceptance criteria). Updates existing IDs and creates code. Outputs working code with @implements traceability tags.
Build customer case studies as marketing and chasm-crossing reference assets during PRD v1.0 Market Adoption. Triggers on requests to build case studies, produce customer stories, create reference content, or when user asks "build a case study", "customer story", "reference account", "case study interview", "before/after story", "social proof page", "logo wall". Outputs CFD-CASE-* evidence entries, GTM-CASE-* marketing assets, and updates ADO-REF-* with story status.
| name | ghm-status-sync |
| description | 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. |
| context | inline |
| allowed-tools | ["Read","Write","Edit","Glob","Grep"] |
Synchronize the README.md Command Center with the current project state after gate advancement or EPIC status changes.
| 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 |
Read these files in order:
README.md (current state)PRD.md (metadata block for lifecycle stage)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 |
Apply synchronization rules:
squad-status): Update agent and EPIC tables:
.claude/agents/: check MEMORY.md mtime for "Last Active", grep EPICs for agent name for "Current EPIC"epics/: read State field, Epic Lead, and Change Log last dateactive (session <2h old), idle (no recent activity), blocked (blocker in session state)| 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 |
DO:
DON'T:
After status sync completes: