deliverable-review SKILL.md skillA
deliverable-review 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/deliverable-review@git:20261027.b46e48dPins git:20261027.b46e48d 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/deliverable-review/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261027.b46e48d, committed Oct 27, 2026
- First version recorded
- Oct 8, 2026
- Size
- 23,618 bytes
- Repository stars
- 6
- License
- MIT
Verify completed work accomplishes what was intended — fresh-eyes sub-agent re-reads output files, traces requirements, checks for gaps and omissions, and reports findings rated High, Medium or Low for the main agent to fix; supports cheaper delta rounds when a caller reviews the same work repeatedly.
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
# Deliverable Review Verify that completed work accomplishes what was intended, and fix any issues found. A sub-agent with a fresh context window re-reads the actual output files — avoiding the bias of the agent that produced the work reviewing it from memory. The main agent orchestrates, then fixes whatever the sub-agent finds. In the standard implementation chain this is the second step (`implement-from-requirements` → `deliverable-review` → `test-hardening`): this skill verifies the deliverable matches intent, then `test-hardening` verifies the tests prove the requirements. (The chain then commits the feature work, runs `refactor-pass`, and pushes a feature branch.) --- ## Process ### Step 1: State the Intent Before reviewing details, articulate the goal of the work in 1-2 sentences: - What were we trying to accomplish? - If there's a ticket, story, or PRD that motivated this work, reference it This becomes the anchor for the entire review. Write it down — you'll come back to it at the end. ### Step 2: Gather Context Collect the information the sub-agent will need: 1. Run `git diff --stat` and `git status` to see what files changed …
Read the whole file at its exact version.
How to install
mdr add ensodynamics/enso-method/deliverable-review@sha256:e60fd39684a4721fThe line at the top of this page pins the label git:20261027.b46e48d, 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_rjluylvxahdu6dxx)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Oct 8, 2026 and Oct 27, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261027.b46e48d latest | 2026-10-27 | b46e48d | 23,618 B | A | view · diff |
| git:20261013.949c97b | 2026-10-13 | 949c97b | 23,394 B | A | view · diff |
| git:20261012.5c8aee5 | 2026-10-12 | 5c8aee5 | 22,528 B | A | view · diff |
| git:20261012.cb8ab22 | 2026-10-12 | cb8ab22 | 21,357 B | A | view · diff |
| git:20261012.eb3c71e | 2026-10-12 | eb3c71e | 10,214 B | A | view · diff |
| git:20261008.813b23c | 2026-10-08 | 813b23c | 10,149 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 (23618 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_rjluylvxahdu6dxx GET https://markdownregistry.com/api/v1/resolve?ref=ensodynamics/enso-method/deliverable-review GET https://markdownregistry.com/api/v1/blob/e60fd39684a4721f5eebf2dc55d0ac02e785669eb045391cda885ddff17451b4
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.