Ghm Self Install logo

Ghm Self Install

Community
mattgierhart
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.

Overview

Publishermattgierhart
RepositoryPRD-driven-context-engineering
Skill nameghm-self-install
Stars
179
Forks
11
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by mattgierhart on GitHub. Read the source before you install it.

Installation

Install the Ghm Self Install AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineering.git /tmp/PRD-driven-context-engineering
mkdir -p .claude/skills
cp -r /tmp/PRD-driven-context-engineering/plugins/prd-ce/skills/ghm-self-install .claude/skills/ghm-self-install
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ghm Self Install in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ghm Self Install on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ghm Self Install is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Frequently asked questions

What does the Ghm Self Install AI skill do?

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.

Why use Ghm Self Install on TypingMind?

Because you install it once and use it with any model. Ghm Self Install is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ghm Self Install in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/plugins/prd-ce/skills/ghm-self-install. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Ghm Self Install?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ghm Self Install?

As many as you like. As long as a model supports skills, you can use Ghm Self Install with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ghm Self Install AI skill free?

Yes. It is published on GitHub by mattgierhart under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇