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.

Install it, pinned
mdr add phuryn/product-engineering/intended-vs-implemented@git:20261108.696d3dd

Pins 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

No tool to install first
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.

The exact contents, by fingerprint
mdr add phuryn/product-engineering/intended-vs-implemented@sha256:2dc5d4f24de7db93

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

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_eolkqtjjuj3xdyv5.svg)](https://markdownregistry.com/a/art_eolkqtjjuj3xdyv5)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
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)

versioncommittedcommitsizeaudit
git:20261108.696d3dd latest2026-11-08 696d3dd 4,044 BA view · diff
git:20261102.f98f1842026-11-02 f98f184 4,147 BA view · diff
git:20261029.89393c82026-10-29 89393c8 4,156 BA view · diff
git:20261028.30d344c2026-10-28 30d344c 3,831 BA view
Keep it current by itself, install once

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.

Install on GitHub

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.

Keep it current by itself

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.

Check a whole project

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

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • 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

GitHub

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

AGENTS.md AGENTS.md file
phuryn/product-engineering · AGENTS.md
git:20261113.cab148b · audit A · 643 stars
CLAUDE.md CLAUDE.md file
phuryn/product-engineering · CLAUDE.md
git:20261028.30d344c · audit B · 643 stars
agent-instructions SKILL.md skill
phuryn/product-engineering · agent-harness/skills/agent-instructions/SKILL.md · Writing or restructuring AGENTS.md or CLAUDE.md, adding a rule ('remember this'), or after an agent ignored a rule it…
git:20261108.6aba512 · audit A · 643 stars
flight-deck SKILL.md skill
phuryn/product-engineering · agent-harness/skills/flight-deck/SKILL.md · 'What's the status', 'where were we', a progress report or status deck; long work that must survive compaction…
git:20261108.4d8bb2b · audit A · 643 stars
guardrail-hooks SKILL.md skill
phuryn/product-engineering · agent-harness/skills/guardrail-hooks/SKILL.md · An agent keeps breaking a rule ('it did it again', 'make this impossible', 'add a hook', 'my hook didn't fire'): make…
git:20261108.063a347 · audit A · 643 stars
handover SKILL.md skill
phuryn/product-engineering · agent-harness/skills/handover/SKILL.md · Write the handover a fresh session starts from: the objective, what is true now, the evidence actually obtained, what…
git:20261108.6aba512 · audit A · 643 stars
retro SKILL.md skill
phuryn/product-engineering · agent-harness/skills/retro/SKILL.md · Build a session's learnings into the setup: its friction, what went wrong and why, then an improved instruction, route…
git:20261108.063a347 · audit A · 643 stars
windows-agent-shell SKILL.md skill
phuryn/product-engineering · agent-harness/skills/windows-agent-shell/SKILL.md · A coding agent on Windows: Git Bash path rewriting, PowerShell quoting and encoding, CRLF. Use when output comes back…
git:20261108.4d8bb2b · audit B · 643 stars
claude-agents SKILL.md skill
phuryn/product-engineering · agent-teams/skills/claude-agents/SKILL.md · 'Ask Claude', 'have Claude build or review this': drive Claude Code headless (claude -p) from another agent as a peer…
git:20261113.cab148b · audit A · 643 stars
codex-agents SKILL.md skill
phuryn/product-engineering · agent-teams/skills/codex-agents/SKILL.md · 'Ask Codex', 'check with Codex', handing Codex a build or review, or stuck between two framings: the Codex CLI as peer…
git:20261114.b203f38 · audit A · 643 stars
delegation SKILL.md skill
phuryn/product-engineering · agent-teams/skills/delegation/SKILL.md · Before spawning a subagent or dispatching a build, review or research, and before trusting its report: the brief, the…
git:20261113.cab148b · audit A · 643 stars
grok-agents SKILL.md skill
phuryn/product-engineering · agent-teams/skills/grok-agents/SKILL.md · 'Ask Grok', 'have Grok build or review this': drive the Grok CLI headless from another agent as a peer, builder or…
git:20261113.1e01017 · audit A · 643 stars

Every file in phuryn/product-engineering

Other files named intended-vs-implemented

intended-vs-implemented SKILL.md skill
phuryn/pm-skills · pm-ai-shipping/skills/intended-vs-implemented/SKILL.md · Moved to phuryn/product-engineering, where it is maintained in the ai-shipping plugin; this copy says where it went and…
git:20261029.53f3494 · audit A · 28,158 stars
intended-vs-implemented SKILL.md skill
sathiaai/adversarial-review · skills/intended-vs-implemented/SKILL.md · Verify what the code actually does against what the docs, roadmap, or handoff claim it does — the code is the source of…
git:20260910.c480f23 · audit A · 3 stars

Browse by kind, by grade A, or by owner.