intended-vs-implemented SKILL.md skillA
intended-vs-implemented from phuryn/product-engineering is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add phuryn/product-engineering/intended-vs-implemented@git:20261108.696d3ddPins git:20261108.696d3dd in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- phuryn/product-engineering
- Path
ai-shipping/skills/intended-vs-implemented/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261108.696d3dd, committed Nov 8, 2026
- First version recorded
- Oct 28, 2026
- Size
- 4,044 bytes
- Repository stars
- 643
- License
- MIT
Auditing AI-built code against its docs: where it does what the docs or permissions don't say, access control against documented roles, cited both sides.
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
# Intended vs. Implemented: Auditing the Gap ## Purpose **Compare implementation with recorded intent to find the gaps linters cannot.** A linter can check internal consistency, but it has no model of what you meant. Important security and correctness bugs live in that gap. Examples include unenforced permissions, publicly callable "cron-only" endpoints and public-only fields leaking private data. This method works only when intent has been written down first. Apply the `shipping-artifacts` skill for that record. That intent axis distinguishes the method from commodity tools. ## Context **Audit documented intent, and report absent or stale docs first.** Use `permissions.md`, `architecture.md`, `variables.md` or the repository's equivalents, under whatever names it uses. You cannot audit intent never recorded. If those docs are absent or stale, make that the first finding and recommend documenting first, then auditing. ## Method …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_eolkqtjjuj3xdyv5/2dc5d4f24de7db93806b9b315ebde3b5e79bb80c3bae7c1f8199d16bd42e44a6.json
Then /plugin install intended-vs-implemented@markdownregistry-eolkqtjjuj3xdyv5 in Claude Code. It installs git:20261108.696d3dd, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add phuryn/product-engineering/intended-vs-implemented@sha256:2dc5d4f24de7db93The line at the top of this page pins the label git:20261108.696d3dd, 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_eolkqtjjuj3xdyv5)
1 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 phuryn/product-engineering/intended-vs-implemented 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 intended-vs-implemented from somewhere else? Ask it: where did my intended-vs-implemented 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 4 versions of this file, between Oct 28, 2026 and Nov 8, 2026, about one every 4 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261108.696d3dd latest | 2026-11-08 | 696d3dd | 4,044 B | A | view · diff |
| git:20261102.f98f184 | 2026-11-02 | f98f184 | 4,147 B | A | view · diff |
| git:20261029.89393c8 | 2026-10-29 | 89393c8 | 4,156 B | A | view · diff |
| git:20261028.30d344c | 2026-10-28 | 30d344c | 3,831 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/intended-vs-implemented/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 (4044 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
phuryn/product-engineering · 643 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_eolkqtjjuj3xdyv5 GET https://markdownregistry.com/api/v1/resolve?ref=phuryn/product-engineering/intended-vs-implemented GET https://markdownregistry.com/api/v1/blob/2dc5d4f24de7db93806b9b315ebde3b5e79bb80c3bae7c1f8199d16bd42e44a6
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.
More from phuryn/product-engineering
Every file in phuryn/product-engineering