technical-design-writing-standards SKILL.md skillA
technical-design-writing-standards 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/technical-design-writing-standards@git:20261026.9ffab64Pins git:20261026.9ffab64 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/technical-design-writing-standards/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261026.9ffab64, committed Oct 26, 2026
- First version recorded
- Oct 13, 2026
- Size
- 14,199 bytes
- Repository stars
- 6
- License
- MIT
Standards and process for writing technical design documents — architecture decisions, interfaces, data models, and integration points, including designs for changes to an existing system. Use to write a design from a refined PRD, or to check one; the draft is committed and handed to review-technical-design, then autonomous-design-refinement. Not implementation instructions.
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
# Technical Design Writing Standards Guidelines for writing technical design documents. --- ## What Is a Technical Design Document? A technical design document describes **how** we're going to build something. This is where technical decisions, interfaces, data models, and architecture choices are documented. The technical design document bridges the gap between the business requirements (the PRD) and the actual implementation. It captures decisions that affect multiple phases or have long-term implications. --- ## When Do You Need a Technical Design Document? Most PRDs need a technical design document. If you're building anything with interfaces, data models, or architecture decisions that need to be agreed upon before implementation, write one. You can skip it when a feature is small, follows an established pattern, and doesn't introduce new interfaces or architectural choices — the PRD is sufficient in those cases. --- ## Writing a Technical Design When asked to write a design, not just check one, this is the whole process. No separate research phase comes first; you read what the PRD's criteria touch, as you need it. ### Existing code: Preserve or Salvage …
Read the whole file at its exact version.
How to install
mdr add ensodynamics/enso-method/technical-design-writing-standards@sha256:a50c91e91773248bThe line at the top of this page pins the label git:20261026.9ffab64, 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_pin2bpvxd5ta47aw)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 13, 2026 and Oct 26, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261026.9ffab64 latest | 2026-10-26 | 9ffab64 | 14,199 B | A | view · diff |
| git:20261022.ad79f04 | 2026-10-22 | ad79f04 | 14,165 B | A | view · diff |
| git:20261018.9c89f88 | 2026-10-18 | 9c89f88 | 13,647 B | A | view · diff |
| git:20261014.85eff88 | 2026-10-14 | 85eff88 | 12,141 B | A | view · diff |
| git:20261013.ce3c32b | 2026-10-13 | ce3c32b | 12,081 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 (14199 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_pin2bpvxd5ta47aw GET https://markdownregistry.com/api/v1/resolve?ref=ensodynamics/enso-method/technical-design-writing-standards GET https://markdownregistry.com/api/v1/blob/a50c91e91773248b97994b8820b5b6dc2534bcc66ccc561bc2826e165f91236d
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.