implementation-readiness-check SKILL.md skillA
implementation-readiness-check 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/implementation-readiness-check@git:20261021.288f2bcPins git:20261021.288f2bc 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/implementation-readiness-check/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261021.288f2bc, committed Oct 21, 2026
- First version recorded
- Oct 6, 2026
- Size
- 20,448 bytes
- Repository stars
- 6
- License
- MIT
Pre-implementation validation gate — surface gaps and unclear assumptions before writing code, with proposed answers, confidence levels, and impact assessments.
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
# Implementation Readiness Check Guidelines for validating understanding before writing code. --- ## What Is This Skill? This skill is the **human-checkpoint validation gate**, for when the user explicitly wants to confirm answers before implementation begins. `autonomous-design-refinement` also runs it once per pass. Its purpose: find gaps and unclear assumptions in the requirements before implementation begins. The AI identifies what's uncertain, proposes how it would handle each item (with a confidence level and impact assessment), and gives the human a chance to confirm or redirect. Implementation moves fast—this is the last chance to get aligned before assumptions become code. Once this check is under way, no implementation begins until it is complete and acknowledged. --- ## When to Use Run this skill **immediately before implementation** (before `phase-split` when the work will be split). Use it when the user explicitly asks for a human review checkpoint. --- ## Context to Review Before proceeding, the AI should review all available materials related to the work being implemented, which may include: - The PRD and/or technical design document for this feature …
Read the whole file at its exact version.
How to install
mdr add ensodynamics/enso-method/implementation-readiness-check@sha256:0f0ee6181299706fThe line at the top of this page pins the label git:20261021.288f2bc, 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_i7pqbfgj7cyzjc2y)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Oct 6, 2026 and Oct 21, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261021.288f2bc latest | 2026-10-21 | 288f2bc | 20,448 B | A | view · diff |
| git:20261013.ce3c32b | 2026-10-13 | ce3c32b | 20,417 B | A | view · diff |
| git:20261008.813b23c | 2026-10-08 | 813b23c | 20,429 B | A | view · diff |
| git:20261006.537f98b | 2026-10-06 | 537f98b | 19,259 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 (20448 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_i7pqbfgj7cyzjc2y GET https://markdownregistry.com/api/v1/resolve?ref=ensodynamics/enso-method/implementation-readiness-check GET https://markdownregistry.com/api/v1/blob/0f0ee6181299706fc2bc6b47b2e3b05e184b2b2cff1307e6cb40acb5b6e6e492
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.