implement-from-discovery SKILL.md skillA
implement-from-discovery 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/implement-from-discovery@git:20261103.fd289f9Pins git:20261103.fd289f9 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/implement-from-discovery/SKILL.md- Versions recorded
- 8
- Latest version
- git:20261103.fd289f9, committed Nov 3, 2026
- First version recorded
- Oct 6, 2026
- Size
- 42,433 bytes
- Repository stars
- 6
- License
- MIT
Implement a fix or improvement identified during research, investigation, or development, or raised in a bug report — not from a PRD authored ahead of time. Verifies alignment with the affected component's PRD/Technical Design, applies the technical-vs-business confidence gate, records the change in the requirements before any code (nothing, an amendment, or a change PRD it writes itself, decided by the skill and never handed back), then implements, tests, commits, runs the refactor pass, and…
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
# Implement From Discovery For implementing changes whose source is something you *discovered* — a bug found mid-investigation, a gap noticed while reading code, a fix identified during a research session — rather than a PRD authored ahead of time. This is the lighter sibling of `implement-from-requirements` (PRD-triggered). It applies the same alignment-checking and technical-vs-business confidence gate that the framework uses everywhere, without its procedural overhead. For the broader framework — the four entities (PRD, Technical Design, Assumptions, and Phase Documents when split), confidence thresholds, the assumptions philosophy, and the session discipline this whole session runs under — see the `implementation-lifecycle` skill, the methodology's umbrella. **Read that first if it isn't already loaded**, and reload it if the session drifts. A user invoking this skill should never need to name another one. --- ## When to Use Use this skill when: - You're already mid-investigation in this conversation and have identified a fix you want to implement now …
Read the whole file at its exact version.
How to install
mdr add ensodynamics/enso-method/implement-from-discovery@sha256:8b9c9de6dbd9b34fThe line at the top of this page pins the label git:20261103.fd289f9, 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_dq5ziyt7ozy35w5i)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 8 versions of this file, between Oct 6, 2026 and Nov 3, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261103.fd289f9 latest | 2026-11-03 | fd289f9 | 42,433 B | A | view · diff |
| git:20261102.32695c3 | 2026-11-02 | 32695c3 | 42,396 B | A | view · diff |
| git:20261027.66c352a | 2026-10-27 | 66c352a | 42,345 B | A | view · diff |
| git:20261024.1d79b09 | 2026-10-24 | 1d79b09 | 34,450 B | A | view · diff |
| git:20261021.288f2bc | 2026-10-21 | 288f2bc | 32,283 B | A | view · diff |
| git:20261012.eb3c71e | 2026-10-12 | eb3c71e | 32,233 B | A | view · diff |
| git:20261008.813b23c | 2026-10-08 | 813b23c | 30,987 B | A | view · diff |
| git:20261006.537f98b | 2026-10-06 | 537f98b | 28,207 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 (42433 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_dq5ziyt7ozy35w5i GET https://markdownregistry.com/api/v1/resolve?ref=ensodynamics/enso-method/implement-from-discovery GET https://markdownregistry.com/api/v1/blob/8b9c9de6dbd9b34f4441abce62541118335e12f895e99e6bd5d72400ee5e2aba
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.