prd-writing-standards SKILL.md skillA
prd-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/prd-writing-standards@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/prd-writing-standards/SKILL.md- Versions recorded
- 11
- Latest version
- git:20261103.fd289f9, committed Nov 3, 2026
- First version recorded
- Oct 14, 2026
- Size
- 38,737 bytes
- Repository stars
- 6
- License
- MIT
Write or check a PRD (Product Requirements Document), the requirements a technical design is then built from. Skimmable — clear business context and testable outcomes without implementation details, invented responsibilities, or step-by-step instructions. Use when the user describes something to build and no PRD exists yet, or to bring an existing PRD up to this standard.
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
# PRD Writing Standards Guidelines for writing PRDs. --- ## What Is a PRD? A PRD (Product Requirements Document) is a high-level description of a product change or capability we're delivering. It answers the questions **"What are we delivering?"** and **"Why are we doing it?"** in plain business language. A PRD should be understandable by product managers, stakeholders, and anyone who needs to know what we're delivering without diving into technical details. --- ## Before You Write: Is This One PRD? A PRD in `docs/prds/` is a medium body of work that ends with something finished that can be promoted to production. It is not the whole application; a bounded change in `docs/changes/` uses the same document set and can be as small as one fix (see "Document Storage Convention"). Before drafting, check the source material against the PRD-sized test in `initiative-breakdown` (Step 2). The usual sign it fails: the work would take many phases before anything finished reaches production, or it bundles several outcomes that could each ship on their own. When it fails, run `initiative-breakdown` first. It cuts the idea into planned PRDs, and this skill then writes each of them. The… …
Read the whole file at its exact version.
How to install
mdr add ensodynamics/enso-method/prd-writing-standards@sha256:428bea1ae0b97707The 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_nwql432h7ozkazae)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 11 versions of this file, between Oct 14, 2026 and Nov 3, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261103.fd289f9 latest | 2026-11-03 | fd289f9 | 38,737 B | A | view · diff |
| git:20261030.099ee29 | 2026-10-30 | 099ee29 | 38,612 B | A | view · diff |
| git:20261028.fdb0982 | 2026-10-28 | fdb0982 | 38,214 B | A | view · diff |
| git:20261027.66c352a | 2026-10-27 | 66c352a | 36,654 B | A | view · diff |
| git:20261027.6176f00 | 2026-10-27 | 6176f00 | 36,030 B | A | view · diff |
| git:20261027.1b24ce8 | 2026-10-27 | 1b24ce8 | 35,150 B | A | view · diff |
| git:20261027.f780e65 | 2026-10-27 | f780e65 | 33,957 B | A | view · diff |
| git:20261026.9ffab64 | 2026-10-26 | 9ffab64 | 33,025 B | A | view · diff |
| git:20261018.9c89f88 | 2026-10-18 | 9c89f88 | 32,755 B | A | view · diff |
| git:20261014.85eff88 | 2026-10-14 | 85eff88 | 32,292 B | A | view · diff |
| git:20261014.50a39e0 | 2026-10-14 | 50a39e0 | 31,874 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 (38737 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_nwql432h7ozkazae GET https://markdownregistry.com/api/v1/resolve?ref=ensodynamics/enso-method/prd-writing-standards GET https://markdownregistry.com/api/v1/blob/428bea1ae0b97707a5aedd09640fc5084712a9d75e03bae52a722b658295cb97
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.