Skip to content
cccskills
FreePublished on GitHub

ghm-self-install

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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md4.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Self-Install

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.sh is the deterministic CLI path. Both read .claude/install-manifest.yaml, so they can't drift. Prefer driving install.sh from this skill; fall back to manual copies only when the script isn't reachable.

Consumes

  • .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.
  • Safety rules from ghm-template-sync Phase "Safety Rules" — never overwrite MEMORY.md, SoT/*, PRD.md, README.md content.

Produces

  • An installed framework in the target repo (no new SoT IDs — this skill places the engine, it doesn't author specs).
  • A verification report (hooks emit valid JSON; readiness.py runs).

Workflow

Phase 1 — Preflight & mode detect

  1. Confirm git, python3, awk are present; warn if the target isn't a git repo.
  2. Detect mode: greenfield (no .claude/) vs brownfield (existing .claude/). Brownfield means merge, never overwrite product.
  3. State the trade explicitly: this installs files only — it costs subscription tokens for the wizard turn, zero API.

Phase 2 — Wizard questions

Ask only what changes the outcome (honor the execution mode's budget):

  • Target directory (default: current repo).
  • Domain profile: product (default) · library · infrastructure · research.
  • Subset [standard+]: keep all 4 agents + all skills (default), or trim to a role subset. Quick mode skips this and installs everything.

Phase 3 — Install (drive 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
  • Show the --dry-run plan first [standard+], then execute.
  • If a framework file shows drift, surface the diff and only re-run with --force after the user confirms (mirrors ghm-template-sync "show diff before destructive").
  • Never write anything in the manifest's never_touch list.

Phase 4 — Verify (trust-but-verify, the Xantham verify-blueprint.sh analog)

  1. Run each .claude/hooks/*.sh in the target; assert valid JSON on stdout.
  2. Run 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.
  3. Print next steps: customize README.md + PRD.md, then "Let's frame the problem".

Anti-patterns

PatternFix
Hardcoding the file list in the skillRead .claude/install-manifest.yaml
Overwriting a brownfield repo's PRD.md/SoTHonor never_touch; seed templates once
Treating readiness BLOCK on a fresh scaffold as a bugIt's the gate working — report the score
Re-implementing copy logic instead of driving install.shOne code path = no drift

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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`.

The English summary is being prepared. Showing the original description.

mattgierhart/PRD-driven-context-engineering181Updated Aug 31, 2026

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.

The English summary is being prepared. Showing the original description.

mattgierhart/PRD-driven-context-engineering181Updated Aug 31, 2026

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.

The English summary is being prepared. Showing the original description.

mattgierhart/PRD-driven-context-engineering181Updated Aug 31, 2026

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.

The English summary is being prepared. Showing the original description.

mattgierhart/PRD-driven-context-engineering181Updated Aug 31, 2026

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.

The English summary is being prepared. Showing the original description.

mattgierhart/PRD-driven-context-engineering181Updated Aug 31, 2026

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".

The English summary is being prepared. Showing the original description.

mattgierhart/PRD-driven-context-engineering181Updated Aug 31, 2026

See all skills by mattgierhart

Report a problem with this skill