prd is agent-read markdown (skill) from ulises-jeremias/agent-toolkit: WHAT — Draft and review a Product Requirements Document (PRD) using the template. Business-level.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# PRD — Product Requirements (WHAT)
**Template:** `references/default-template.md` — local reference, kept up to date with the standard structure.
## Default guardrails (before any final content)
1. Apply **`output-handshake`**: confirm **where** the final PRD will be stored (path, Doc page, task, paste-only, etc.) and that a **human** will review. Engagements may store PRDs in different places; do not assume.
2. Then follow the steps below.
## When to use
- A feature or product increment needs a **shared agreement** on scope, users, and acceptance.
- The team must **trace** work from PRD → implementation → tests.
- An engagement uses an **Operations**-style doc hub with linked requirements documents.
## Instructions
1. **Open the PRD template** (`references/default-template.md`) and keep section headings **aligned** with it: Objective, User flow / Personas, Entities & use cases, Acceptance criteria, Edge cases, Integrations, Timeline, Approvals.
2. For **discovery** in an existing repository, delegate repository inspection to **`assistant`**; cite `AGENTS.md` and test/lint commands from the project.
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_mqq5mazboxnrx43q
GET https://markdownregistry.com/api/v1/resolve?ref=ulises-jeremias/agent-toolkit/prd
GET https://markdownregistry.com/api/v1/blob/0d93a06db51f7c175142709917107d32be3f14cc8607bf0ac20ce9fd49a3110b
Your agent 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.
ulises-jeremias/agent-toolkit · plugins/agent-toolkit-complete/.github/skills/adr/SKILL.md · WHAT — Create and maintain Architecture Decision Records (ADRs) per the process. Covers when
ulises-jeremias/agent-toolkit · plugins/agent-toolkit-complete/.github/skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe…
ulises-jeremias/agent-toolkit · plugins/agent-toolkit-complete/.github/skills/bug/SKILL.md · WHAT - Draft and review bugs using the Bug Template; classifies whether an issue should be
ulises-jeremias/agent-toolkit · plugins/agent-toolkit-complete/.github/skills/c4-model/SKILL.md · WHAT — C4 model methodology (Context, Container, Component, Code) guidance — what to draw at each level, when, and how…
ulises-jeremias/agent-toolkit · plugins/agent-toolkit-complete/.github/skills/chrome-devtools/SKILL.md · Use Chrome DevTools MCP to control and inspect a live Chrome instance for network, console, performance, rendering, and…
sethgammon/citadel · skills/prd/SKILL.md · Generates a Product Requirements Document from a natural language app description. Asks clarifying questions…
openhands/extensions · skills/prd/SKILL.md · Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project…
cryndoc/polisade-orchestrator · skills/prd/SKILL.md · Create a full Product Requirements Document (PRD-NNN) via a structured PM interview — for large initiatives that…
byjunyoung/claude-product-skills · plugins/pm/skills/prd/SKILL.md · Writes a product requirements document against a format, or fills out an existing one. Gathers and analyzes code repos…
