Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD.
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 Generator
Create detailed Product Requirements Documents that are clear, actionable, and suitable for implementation.
---
## The Job
1. Receive a feature description from the user
2. Ask 3-5 essential clarifying questions (with lettered options)
3. Generate a structured PRD based on answers
4. Save to `prd-[feature-name].md` in the repository root
**Important:** Do NOT start implementing. Just create the PRD.
---
## Step 1: Clarifying Questions
Ask only critical questions where the initial prompt is ambiguous. Focus on:
- **Problem/Goal:** What problem does this solve?
- **Core Functionality:** What are the key actions?
- **Scope/Boundaries:** What should it NOT do?
- **Success Criteria:** How do we know it's done?
### Format Questions Like This:
```
1. What is the primary goal of this feature?
A. Improve user onboarding experience
B. Increase user retention
C. Reduce support burden
D. Other: [please specify]
2. Who is the target user?
A. New users only
B. Existing users only
C. All users
D. Admin users only
3. What is the scope?
A. Minimal viable version
B. Full-featured implementation
C. Just the backend/API
D. Just the UI
…
The line at the top of this page pins the label git:20260414.e9ca940, 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.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (6897 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
GitHub
openhands/extensions · 179 stars · license MIT · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fendjhtzwyyiml7q
GET https://markdownregistry.com/api/v1/resolve?ref=openhands/extensions/prd
GET https://markdownregistry.com/api/v1/blob/5de2431f9ceb205f76978940b7c1c65e503bb9603410088b8af75bdf2749eb61
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.
openhands/extensions · plugins/cobol-modernization/skills/build-setup/SKILL.md · Set up build environment and test fixtures for COBOL-to-Java migrations. Creates compilation infrastructure for both…
openhands/extensions · plugins/cobol-modernization/skills/mainframe-planning/SKILL.md · Create a transformation guide for replacing mainframe-specific COBOL constructs with standard COBOL equivalents. Use…
openhands/extensions · plugins/cobol-modernization/skills/to-java-migration/SKILL.md · Migrate COBOL code to idiomatic Java, preserving business logic while following Java best practices. Use for COBOL…
openhands/extensions · plugins/migration-scoring/skills/migration-mapping/SKILL.md · Create a mapping from source language files to target language files for code migrations. Use when evaluating or…
openhands/extensions · plugins/migration-scoring/skills/migration-report/SKILL.md · Generate a comprehensive migration report summarizing quality scores and providing recommendations. Use after scoring a…
openhands/extensions · plugins/migration-scoring/skills/score-quality/SKILL.md · Score code migration quality based on coverage and correctness. Evaluates how well target code represents source…
openhands/extensions · plugins/migration-scoring/skills/score-style/SKILL.md · Score migrated code against style guidelines and best practices. Evaluates code quality independent of functional…
sethgammon/citadel · skills/prd/SKILL.md · Generates a Product Requirements Document from a natural language app description. Asks clarifying questions…
skillmds/skillmd · plugins/create-prd-from-idea/skills/sdiamante13-prd/SKILL.md · Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project…
