Ghm Status Sync logo

Ghm Status Sync

Community
mattgierhart
ghm-status-sync

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.

Overview

Publishermattgierhart
RepositoryPRD-driven-context-engineering
Skill nameghm-status-sync
Stars
179
Forks
11
Bundled files
3
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.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

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

Installation

Install the Ghm Status Sync 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-status-sync .claude/skills/ghm-status-sync
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ghm Status Sync 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 Status Sync 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 Status Sync 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.

Status Sync

Synchronize the README.md Command Center with the current project state after gate advancement or EPIC status changes.

Workflow Overview

  1. Load Context → Read README.md, PRD.md metadata, Active EPIC Session State section
  2. Extract State → Pull lifecycle stage, blockers, metrics
  3. Update Dashboard → Sync README sections with current truth

Core Output Template

ElementDefinitionEvidence
Lifecycle StageCurrent PRD version from PRD.mdCurrent Lifecycle Gate: v0.X
Gate StatusVisual progress indicators🟢 Complete / 🟡 In Progress / ⚪ Pending
Active EPICCurrent work from EPIC headerEPIC-XX: Title
BlockersOpen blockers from EPIC Session State sectionList with severity

Step 1: Load Context

Read these files in order:

  1. README.md (current state)
  2. PRD.md (metadata block for lifecycle stage)
  3. Active EPIC Session State section (blockers, progress)

Checklist

  • README.md loaded
  • PRD.md metadata extracted
  • Active EPIC identified and Session State section read

Step 2: Extract Current State

Pull authoritative values:

FieldSource
Lifecycle StagePRD.md Current Lifecycle Gate
Gate ProgressPRD.md gate table
Active EPICREADME.md Active Work section
BlockersEPIC Session State section
MetricsREADME.md Truth Table

Step 3: Update README Dashboard

Apply synchronization rules:

  1. Lifecycle Stage: Update header to match PRD.md
  2. Gate Table:
    • 🟢 = Passed gates (all criteria met)
    • 🟡 = Current gate (in progress)
    • ⚪ = Future gates (not started)
  3. Active EPIC: Update metadata in Active Work section
  4. Blockers: Sync from EPIC Session State section
  5. Squad Status (Section: squad-status): Update agent and EPIC tables:
    • For each agent in .claude/agents/: check MEMORY.md mtime for "Last Active", grep EPICs for agent name for "Current EPIC"
    • For each EPIC in epics/: read State field, Epic Lead, and Change Log last date
    • Status values: active (session <2h old), idle (no recent activity), blocked (blocker in session state)

Quality Gates

Pass Checklist

  • README lifecycle stage matches PRD.md
  • Gate indicators are accurate (no 🟢 on incomplete gates)
  • Active EPIC reference is current
  • Blockers reflect actual state

Testability Check

  • Can be validated by comparing README to PRD.md
  • Gate status is traceable to gate criteria

Anti-Patterns

PatternExampleFix
Stale gate status🟢 on gate with missing criteria→ Verify all criteria before marking complete
Missing blockersEPIC has blockers, README shows none→ Always sync from EPIC Session State section
Wrong EPIC referenceREADME points to closed EPIC→ Check EPIC status before updating

Boundaries

DO:

  • Status synchronization
  • Link updates
  • Gate progression indicators

DON'T:

  • Content changes to descriptions
  • Create new sections
  • Modify PRD.md (read-only source)

Handoff

After status sync completes:

  • README.md is current and accurate
  • Ready for next work session
  • Gate-check skill can validate if advancing

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Ghm Status Sync AI skill do?

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.

Why use Ghm Status Sync on TypingMind?

Because you install it once and use it with any model. Ghm Status Sync 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 Status Sync 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-status-sync. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Ghm Status Sync?

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 Status Sync?

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

Is the Ghm Status Sync 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 👇