From PRD-Driven Context Engineering
Installs the PRD-Driven Context Engineering methodology into a fresh or existing repository via an interactive wizard. Seeds .claude/ hooks, skills, agents, rules, and scripts without overwriting product content.
How this skill is triggered — by the user, by Claude, or both
Slash command
/prd-ce:ghm-self-installThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Install the methodology into a target repo from the **install manifest**, the way
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 |
npx claudepluginhub mattgierhart/prd-driven-context-engineering --plugin prd-ceSeeds a greenfield repository with the PRD-Driven Context Engineering scaffold: PRD.md, SoT/ knowledge files, EPIC templates, domain config, and agent memory starters. Invoked via /prd-ce:init for project initialization.
Initializes project configuration by auto-detecting framework, replacing CLAUDE.md placeholders, and installing rules, hooks, and scripts.
Installs context files for Claude Code projects defining standards, security, and workflows. Checks git/node, prompts for local/global and profile (standard/extended/all), runs bash/node scripts.