gdd SKILL.md skillA
gdd from wxxb789/hoa is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wxxb789/hoa/gdd@git:20261119.6fef477Pins git:20261119.6fef477 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wxxb789/hoa
- Path
skills/gdd/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261119.6fef477, committed Nov 19, 2026
- First version recorded
- Nov 17, 2026
- Size
- 9,272 bytes
- Repository stars
- 3
- License
- MIT
Land a written, machine-checkable increment in a repo end to end — one goal contract, one fresh authoring-agent run per stage, gates the operator re-runs, a scripted merge gate, and a durable stage ledger so a later session can resume in three commands. Use when an increment is delegated end to end, including the merge. Do not use for one-line fixes, exploration with no acceptance criteria, or work no machine can check (that is a conversation, not a delivery).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Goal-driven delivery
One written increment (a goal), authored by a coding agent, verified and landed by the operator, with
the loop running end to end and no per-step approval. **Done** is merged *and* the next goal branched
off the merged head — an open PR is not done.
## When to Use
- "Start the next goal", "run the goal-driven flow", "finish this the usual way".
- 中文同义说法同样触发:`开始下一个 goal`、`推进 goal driven 流程`、`按老流程把这个做完`。
- Any multi-hour repo increment: a feature, a research-feasibility study, a migration, a docs
rewrite — anything with a written completion contract and machine-checkable gates.
- A repo where the operator delegates end to end, including the merge.
Not for: one-line fixes, exploratory poking with no acceptance criteria, or work whose result no
machine can check.
## Stage order — fixed, no skipping
```
contract → implement → verify → simplify-report → apply → code-review-report → fix
→ gates → PR → babysit → merge → reset
```
Both two-phase steps are mandatory: an unapplied report or an unfixed review does not close a stage.
Caps: `implement` 2 recovery attempts, `simplify` 2 rounds, `review→fix` 2 rounds. On a third round,
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_wajp2nswvl6rcixc/35b12a39d512a8861cd519b12512bf673424869ebf4c3e1dc6ce7f14ce07ed1c.json
Then /plugin install gdd@markdownregistry-wajp2nswvl6rcixc in Claude Code. It installs git:20261119.6fef477, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add wxxb789/hoa/gdd@sha256:35b12a39d512a886The line at the top of this page pins the label git:20261119.6fef477, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_wajp2nswvl6rcixc)
0 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in wxxb789/hoa/gdd since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of gdd from somewhere else? Ask it: where did my gdd come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Nov 17, 2026 and Nov 19, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261119.6fef477 latest | 2026-11-19 | 6fef477 | 9,272 B | A | view · diff |
| git:20261118.d4726de | 2026-11-18 | d4726de | 9,272 B | A | view · diff |
| git:20261118.7b3f760 | 2026-11-18 | 7b3f760 | 9,315 B | A | view · diff |
| git:20261117.5d6cc46 | 2026-11-17 | 5d6cc46 | 9,155 B | A | view · diff |
| v0.1.66 | 2026-11-17 | fd3bd52 | 9,159 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/gdd/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9272 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
wxxb789/hoa · 3 stars · license MIT · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wajp2nswvl6rcixc GET https://markdownregistry.com/api/v1/resolve?ref=wxxb789/hoa/gdd GET https://markdownregistry.com/api/v1/blob/35b12a39d512a8861cd519b12512bf673424869ebf4c3e1dc6ce7f14ce07ed1c
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.