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.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Install the methodology into a target repo from the install manifest, the way Xantham's blueprint installs from markdown: the agent runtime is the installer, so the whole thing runs inside your Claude Code subscription — no API key, no metered calls, no service to stand up.
Two paths, one manifest. This skill is the interactive path.
install.shis the deterministic CLI path. Both read.claude/install-manifest.yaml, so they can't drift. Prefer drivinginstall.shfrom this skill; fall back to manual copies only when the script isn't reachable.
.claude/install-manifest.yaml — authoritative framework / template_seed /
never_touch lists (the keystone; never hardcode file lists).install.sh — the deterministic installer this skill normally drives.ghm-template-sync Phase "Safety Rules" — never overwrite
MEMORY.md, SoT/*, PRD.md, README.md content.readiness.py runs).git, python3, awk are present; warn if the target isn't a git repo..claude/) vs brownfield (existing .claude/).
Brownfield means merge, never overwrite product.Ask only what changes the outcome (honor the execution mode's budget):
product (default) · library · infrastructure · research.[standard+]: keep all 4 agents + all skills (default), or trim to a role
subset. Quick mode skips this and installs everything.install.sh)Run the deterministic installer so behavior matches the CLI path exactly:
bash install.sh --target <DIR> --profile <PROFILE> # add --dry-run to preview
--dry-run plan first [standard+], then execute.--force
after the user confirms (mirrors ghm-template-sync "show diff before destructive").never_touch list.verify-blueprint.sh analog).claude/hooks/*.sh in the target; assert valid JSON on stdout.python scripts/readiness.py run — a non-zero exit on an empty scaffold is the
expected BLOCK gate (no content yet), not a failure. Report the score.README.md + PRD.md, then "Let's frame the problem".| Pattern | Fix |
|---|---|
| Hardcoding the file list in the skill | Read .claude/install-manifest.yaml |
Overwriting a brownfield repo's PRD.md/SoT | Honor never_touch; seed templates once |
| Treating readiness BLOCK on a fresh scaffold as a bug | It's the gate working — report the score |
Re-implementing copy logic instead of driving install.sh | One code path = no drift |
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Validates gate criteria before PRD lifecycle advancement by delegating to the readiness scoring pipeline (scripts/readiness.py). Returns a graduated PASS / WARN / BLOCK verdict with top blockers and their causal chain. Triggers before advancing from v0.X to v0.Y or explicit `/ghm-gate-check`.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
Validates and registers new SoT IDs with cross-reference integrity. Triggers when creating BR-XXX, UJ-XXX, API-XXX, or CFD-XXX entries. Outputs formatted SoT entry with validated cross-references.
中文简介正在准备中。当前显示原文说明。
Creates new Source of Truth (SoT) files when existing templates don't fit your needs. Triggers on requests to create a new SoT file, add a new artifact type, or when user says "I need to track [X] but there's no SoT for it", "create SoT", "new source of truth". Outputs a properly structured SoT.*.md file with ID prefix, frontmatter, and update protocol.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
Detect template version drift and guide migration to the latest template version. Compares current repo against the template, identifies what's outdated, and automates safe updates while protecting product-specific content. Triggers on requests to sync with template, update template version, check for template drift, or when user asks "sync template", "update to v3", "template drift", "check template version".
中文简介正在准备中。当前显示原文说明。