review-technical-design SKILL.md skillA
review-technical-design 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/review-technical-design@git:20261018.9c89f88Pins git:20261018.9c89f88 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/review-technical-design/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261018.9c89f88, committed Oct 18, 2026
- First version recorded
- Oct 6, 2026
- Size
- 36,702 bytes
- Repository stars
- 6
- License
- MIT
Senior review that revises a freshly drafted technical design in place, between technical-design-writing-standards and autonomous-design-refinement — an independent would-I-build-it-this-way architecture pass, load-bearing claims verified against the real codebase and infrastructure (read-only), data-model changes tested against the current ecosystem and future evolution, and the house engineering standards applied. Fixes every gap and false claim, swaps a working choice only for a verified…
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
# Review a Technical Design Document ## Where this fits, and when to run it Run it after `technical-design-writing-standards` has drafted and committed a design, and before `autonomous-design-refinement`. The drafting skill starts it; run it by hand on a design that skipped it. **It runs in a fresh context** — a subagent, or a new chat — never in the session that wrote the design. The architecture pass starts by sketching an independent design before reading this one, and a session that just wrote the design can't. **It skips itself** when the design follows an established pattern and makes no decision that is expensive to reverse: no new service, no new or changed schema or data model, no new public interface. Say so in one line, record it with an empty commit (Phase 6), and stop. The order matters. `autonomous-design-refinement` fills gaps *inside* the design's frame and deliberately never asks "would it be better if…". This skill is the one that questions the frame. Refining a design that is then restructured wastes the refinement. Designs are too long for a person to read in full, and an AI-written design reads …
Read the whole file at its exact version.
How to install
mdr add ensodynamics/enso-method/review-technical-design@sha256:3796cc0d9077c01cThe line at the top of this page pins the label git:20261018.9c89f88, 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_u7btlhgvln4x4xwt)
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 18, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261018.9c89f88 latest | 2026-10-18 | 9c89f88 | 36,702 B | A | view · diff |
| git:20261013.ce3c32b | 2026-10-13 | ce3c32b | 31,077 B | A | view · diff |
| git:20261008.813b23c | 2026-10-08 | 813b23c | 31,095 B | A | view · diff |
| git:20261006.537f98b | 2026-10-06 | 537f98b | 30,842 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 (36702 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_u7btlhgvln4x4xwt GET https://markdownregistry.com/api/v1/resolve?ref=ensodynamics/enso-method/review-technical-design GET https://markdownregistry.com/api/v1/blob/3796cc0d9077c01c90eb1b0ec0772cf908c86d5872bccfa7ce3575e536f8d130
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.