delivery-audit SKILL.md skillA
delivery-audit from ensodynamics/enso-method is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ensodynamics/enso-method/delivery-audit@git:20261028.8c7215fPins git:20261028.8c7215f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ensodynamics/enso-method
- Path
skills/delivery-audit/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261028.8c7215f, committed Oct 28, 2026
- First version recorded
- Oct 19, 2026
- Size
- 20,020 bytes
- Repository stars
- 6
- License
- MIT
Independent check, once every planned phase of a PRD is closed, that each acceptance criterion is actually built — every required part present and reachable from the entry point a user or calling system would use, not logic nothing calls. Sub-agents read the criteria from the PRD themselves and trace each one through the code, in fresh rounds until one finds no new gap; the main agent confirms every gap, and checks its siblings, before acting on it. It writes no code. Gaps become completion…
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
# Delivery Audit An independent check, once a PRD's planned phases are all closed, that every acceptance criterion is built. It asks one question of each criterion: **could a user, or the system the criterion is about, get this behavior from the code as it stands?** It grades nothing about tests; `test-audit` does that next. Gaps become completion phases at the end of the plan, built by `implement-from-requirements` like any other phase. Every phase already ran `deliverable-review`. That is not enough on its own: - **Each review saw one phase's diff.** Nothing re-checks a criterion a later phase broke, a cross-cutting criterion across all the phases, or a part that fell between two of them. - **A phase's Closed line is written by the session that built it.** Its own wrap-up decided the criteria were met. - **Gaps are usually partial, not total.** The logic exists but nothing calls it; the main path works and the error case the criterion names doesn't; one of two channels is wired. A missing feature is easy to notice, a half-wired one is not. …
Read the whole file at its exact version.
How to install
mdr add ensodynamics/enso-method/delivery-audit@sha256:1b2fb8f3c2e3e3f5The line at the top of this page pins the label git:20261028.8c7215f, 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_jnc5ph3cspkh7ylt)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Oct 19, 2026 and Oct 28, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.8c7215f latest | 2026-10-28 | 8c7215f | 20,020 B | A | view · diff |
| git:20261025.35e2a7d | 2026-10-25 | 35e2a7d | 17,183 B | A | view · diff |
| git:20261019.a149e63 | 2026-10-19 | a149e63 | 16,499 B | A | view |
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 (20020 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
ensodynamics/enso-method · 6 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jnc5ph3cspkh7ylt GET https://markdownregistry.com/api/v1/resolve?ref=ensodynamics/enso-method/delivery-audit GET https://markdownregistry.com/api/v1/blob/1b2fb8f3c2e3e3f59b41b4d8a038f505b8050bd3ef2d90520789430e00c0a92f
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.