using-the-enso-method SKILL.md skillA
using-the-enso-method 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/using-the-enso-method@git:20261102.32695c3Pins git:20261102.32695c3 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/using-the-enso-method/SKILL.md- Versions recorded
- 11
- Latest version
- git:20261102.32695c3, committed Nov 2, 2026
- First version recorded
- Oct 23, 2026
- Size
- 17,187 bytes
- Repository stars
- 6
- License
- MIT
Where to start and what comes next in the Enso Method — which skill runs at each stage, in what order, and where the user's review is recommended. Use when the user asks to use the Enso Method, asks "where do I start" or "what's next", or hands over requirements, an idea or a brief without naming a skill. A map only; each skill it names owns its own procedure.
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
# Using the Enso Method
The Enso Method builds software from requirements through a fixed order of documents, each written by one skill. Two points are recommended for the user's review, the refined PRD and the reviewed technical design; neither is required, and nothing waits on them unless the user asks it to. Beyond those, the user is not asked about requirements again. This skill is the map: it says which skill comes next and nothing about how that skill works. Load the skill it names for that. The philosophy and session discipline (assumptions, confidence thresholds, No Loose Ends) live in `implementation-lifecycle`.
## Find Where the Work Stands
Read the repo before choosing. Everything for one piece of work lives in `docs/prds/{name}/`, or `docs/changes/{name}/` for a bounded change, or wherever the repo already keeps its documents; an idea cut into several PRDs also has `docs/initiatives/{name}/` (`docs/roadmaps/{name}/` in older repos), and raw material that went through `requirements-intake` has its record in `source-material/{name}/`. When several rows match, the furthest stage reached (the lowest row) wins, except that a pending feedback-changes file (the last row)…
…Read the whole file at its exact version.
How to install
mdr add ensodynamics/enso-method/using-the-enso-method@sha256:d5d90a40b4e21a26The line at the top of this page pins the label git:20261102.32695c3, 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_5x7bkdc5pkqtgxve)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 11 versions of this file, between Oct 23, 2026 and Nov 2, 2026, about one every day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261102.32695c3 latest | 2026-11-02 | 32695c3 | 17,187 B | A | view · diff |
| git:20261030.0d2c5d0 | 2026-10-30 | 0d2c5d0 | 16,909 B | A | view · diff |
| git:20261028.fdb0982 | 2026-10-28 | fdb0982 | 16,723 B | A | view · diff |
| git:20261027.b46e48d | 2026-10-27 | b46e48d | 15,703 B | A | view · diff |
| git:20261027.66c352a | 2026-10-27 | 66c352a | 15,152 B | A | view · diff |
| git:20261027.6176f00 | 2026-10-27 | 6176f00 | 14,826 B | A | view · diff |
| git:20261026.1f2fa83 | 2026-10-26 | 1f2fa83 | 13,896 B | A | view · diff |
| git:20261026.9ffab64 | 2026-10-26 | 9ffab64 | 11,113 B | A | view · diff |
| git:20261025.35e2a7d | 2026-10-25 | 35e2a7d | 10,932 B | A | view · diff |
| git:20261023.3fcf75c | 2026-10-23 | 3fcf75c | 10,817 B | A | view · diff |
| git:20261023.bb10f2d | 2026-10-23 | bb10f2d | 10,362 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 (17187 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_5x7bkdc5pkqtgxve GET https://markdownregistry.com/api/v1/resolve?ref=ensodynamics/enso-method/using-the-enso-method GET https://markdownregistry.com/api/v1/blob/d5d90a40b4e21a261aeecbd3d562f0000379a4f237476442e83348aed2ce502a
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.