write-prd SKILL.md skillA
write-prd from kdy1/kdy1-scripts is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kdy1/kdy1-scripts/write-prd@git:20261018.f796075Pins git:20261018.f796075 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kdy1/kdy1-scripts
- Path
skills/write-prd/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261018.f796075, committed Oct 18, 2026
- First version recorded
- Aug 24, 2026
- Size
- 8,561 bytes
- Repository stars
- 32
- License
- none declared
Product requirements decision capture and GitHub issue creation. Use only when a human explicitly invokes `$write-prd`; never select this skill automatically from feature, planning, PRD, or issue-creation task similarity. When explicitly invoked, define or finalize a PRD, turn a feature idea into a decision-complete GitHub issue, and resolve applicable product, technical, operational, rollout, observability, support, documentation, and testing decisions.
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 PRD ## Goal Turn a feature request into a complete PRD-backed GitHub issue. Do not invent material defaults. Every applicable functional and operational decision must be answered by the user, explicitly marked not applicable by the user, or directly determined by an authoritative repository contract before creating the issue. ## Required References Read these files before asking PRD questions or writing the issue: - `references/question-ledger.md` for the required decision ledger. - `references/issue-template.md` for the fallback GitHub issue shape. ## Operating Rules - Follow all active system, developer, repository, and scoped instructions. - Read the target repository's authoritative docs, contracts, contribution guidance, issue templates, and metadata conventions for the affected area before finalizing decisions. - Resolve the GitHub target from an explicit repository or issue URL, otherwise from the current Git remote. Ask the user before filing when no unique target can be established. …
Read the whole file at its exact version.
How to install
mdr add kdy1/kdy1-scripts/write-prd@sha256:40a6165d09679559The line at the top of this page pins the label git:20261018.f796075, 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_jf4yllb5wj34deot)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 24, 2026 and Oct 18, 2026, about one every 27 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261018.f796075 latest | 2026-10-18 | f796075 | 8,561 B | A | view · diff |
| git:20260909.eacb25a | 2026-09-09 | eacb25a | 7,202 B | A | view · diff |
| git:20260824.9ad4ffe | 2026-08-24 | 9ad4ffe | 5,860 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 (8561 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
kdy1/kdy1-scripts · 32 stars · license none declared · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jf4yllb5wj34deot GET https://markdownregistry.com/api/v1/resolve?ref=kdy1/kdy1-scripts/write-prd GET https://markdownregistry.com/api/v1/blob/40a6165d096795598683282eccceee310367d21f383f1983db0e054f9ef511f5
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 kdy1/kdy1-scripts
Every file in kdy1/kdy1-scripts