write-prd SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
write-prd from tam159/next-role is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tam159/next-role/write-prd@git:20260719.ec018caPins git:20260719.ec018ca in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tam159/next-role
- Path
.claude/skills/write-prd/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260719.ec018ca, committed Jul 19, 2026
- First version recorded
- May 23, 2026
- Size
- 9,158 bytes
- Repository stars
- 62
- License
- MIT
Generate a concise PRD for the feature built in the current session and save it to docs/prd/. Use this skill whenever the user says "write a PRD", "generate a PRD", "/write-prd", asks to document the feature just shipped, or otherwise requests a product/feature spec for work done in this session — even if they don't name the docs/prd/ folder.
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
Write a PRD that captures the feature implemented in the current session, in the house style of `docs/prd/`. That folder is an **OKF (Open Knowledge Format) knowledge bundle** — see `docs/prd/README.md` — so every PRD is a markdown concept document with YAML frontmatter, and the relative links between PRDs draw the edges of the bundle's knowledge graph. The audience is a future developer or AI agent reading the file cold — months later, after the code has drifted. The point is not to restate what the diff shows; it is to capture the *why* and the *non-obvious decisions* that the code alone can't explain. The frontmatter `description` doubles as the PRD's one line in `docs/prd/index.md` — it is what an AI agent reads to decide whether to open the file at all, so make it carry the feature's essence. ## Workflow 1. **Anchor on the existing style.** Read at least one existing PRD in `docs/prd/` (e.g. `10_print_file_as_pdf.md` or `03_jd_url_extraction.md`) before writing. Match its tone, density, and section order. Do not invent new sections. 2. **Mine the session for content.** The conversation history is your source material — pull from: …
Read the whole file at its exact version.
How to install
mdr add tam159/next-role/write-prd@sha256:2a3716ad30d96104The line at the top of this page pins the label git:20260719.ec018ca, 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_d2o4llaah4mxiifc)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 23, 2026 and Jul 19, 2026, about one every 57 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260719.ec018ca latest | 2026-07-19 | ec018ca | 9,158 B | A | view · diff |
| git:20260523.d81ba09 | 2026-05-23 | d81ba09 | 5,542 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 (9158 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
tam159/next-role · 62 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_d2o4llaah4mxiifc GET https://markdownregistry.com/api/v1/resolve?ref=tam159/next-role/write-prd GET https://markdownregistry.com/api/v1/blob/2a3716ad30d961041cb2cf59966e700234a12ed36e0ca3db255d1bb1d23ba2c3
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.
More from tam159/next-role
Every file in tam159/next-role