prd
Skill2 starsChanged 49 days agoMITView on GitHub
Draft a PRD from an Idea file where the "Why" section is 100% cited from the graph and open questions come from the Research backlog. Use when the user runs /prd or asks to write a product requirements doc / spec for an idea.
125 other projects use a version of this.
Adopted by
Most recently taken up by
- Adelie-Squad/solosquadtheir own version, first seen Nov 8, 2026
- shaqmughal/seekstonetheir own version, first seen Nov 8, 2026
- lhbsaa/apex-unifiedtheir own version, first seen Nov 8, 2026
- Jasenpan1987/multi-codetheir own version, first seen Nov 8, 2026
- joeldevz/skynex-pitheir own version, first seen Nov 8, 2026
- insight68/Skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use context-optimize, usecase and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ibahgatSkillcontext-optimize
Improve context efficiency and cache stability for long or complex sessions.
Also in 3 projects that use this
gabriellstSkillusecase
Create an application use case. Use when implementing business operations like CreateOrder, ProcessPayment, CancelBooking. Use this skill for any command/mutation that orchestrates domain logic, whether simple CRUD or complex multi-step transactions with sagas. Dispatch hub — routes to typescript/go variants by file extension.
Also in 3 projects that use this
jidechaoSkillmodern-go
Modernize Go code by applying version-appropriate idioms and APIs (gofix-style transformations). Scans go.mod for the Go version, then transforms Go source files to use modern patterns—from Go 1.0 through 1.26+. Use when the user says "现代化","现代Go语言", "地道的", "idiomatic", "modernize", "modern-go", "update Go code", "gofix", or wants to upgrade Go idioms.
Also in 3 projects that use this
ulises-jeremiasSkilltrd
WHAT — Draft and review a Technical Requirements Document (TRD) using the template, typically
Also in 3 projects that use this
jidechaoSkillloop-it
Automated issue loop with checkpoint/resume: fetch open GitHub issues → dependency-aware topological sort → implement each issue end-to-end → review with /review-it → document with /note-it → ship with /ship-it → repeat. Persists state to .loop-state.json for crash recovery. Triggers on: loop-it, loop issues, auto implement, 批量实现, 循环实现, 实现所有issue, 恢复循环, resume loop.
Also in 3 projects that use this
snarktankSkillralph
Convert PRDs to prd.json format for the Ralph autonomous agent system. Use when you have an existing PRD and need to convert it to Ralph's JSON format. Triggers on: convert this prd, turn this into ralph format, create prd.json from this, ralph json.
Also in 16 projects that use this
- +2 more from jidechao
Other versions125 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 125
- github/awesome-copilot★ 41ksame name
- snarktank/ralph★ 22ksame name
- SethGammon/Citadel★ 927same name
- smallnest/autoresearch★ 571same name
- snarktank/compound-product★ 542same name
- CatCatUncle/openworkbuddy★ 398same name
- smallnest/goal-workflow★ 283same name
- OffchainLabs/arbitrum-docs★ 252same name
- julianromli/ai-skills★ 215same name
- golbin/agent-skills★ 214same name
115 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- affinitySkill
- ai-personaSkill
- analytics-syncSkill
- backlogSkill
- catalogSkill
- cold-startSkill
- contradictionsSkill
- demo-dataSkill
- dovetail-syncSkill
- exportSkill
- extract-findingsSkill
- feature-panelSkill
- forget-participantSkill
- graph-lintSkill
- interview-guideSkill
- journey-mapSkill
- opportunity-treeSkill
- persona-avatarSkill
- persona-querySkill
- persona-talkSkill
- persona-voiceSkill
- persona-workshopSkill
- prioritizeSkill
- researcherSkill
- retentionSkill
- source-syncSkill
- subject-accessSkill
- welcomeSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 102 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Read the Idea + linked sources + persona sections + backlog rows + Product Context.md.
“Common” is measured: kept by at least 6 in 10 of the 102 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
prd — A PRD whose "Why" is fully cited
Generate a draft PRD from an Ideas/ file. The differentiator: the Why section contains only claims that exist in the graph, each cited — and the Open questions section shows engineering exactly what's still unvalidated, pulled from Research backlog.md. A PRD that admits what it doesn't know.
Trigger
/prd Ideas/Idea3 Context mode (Listening Modes).mdStructure of the draft
- Problem statement — the When/I want/So that, expanded into prose from the linked Pain and its Signal (verbatim quote included — a real user's sentence beats ten bullets).
- Why now / evidence — every linked Evidence and Signal, one line each: claim + source + Level (analyst doc — codes fine) + freshness note where the 3-month rule bites. Nothing uncited enters this section, period.
- Who it's for — the persona(s) whose Pains link here (run the logic of
/feature-panelbriefly: fit, indifferent, conflict — including any persona this could hurt). - Scope sketch — reasonable functional bullets from the idea; clearly labeled as proposal, not research (this is the one section allowed to go beyond the data, and it says so).
- Success metrics — from the idea's
Metric to watch+ how to verify via/analytics-sync; baseline value if an internal Evidence already holds one. - Open questions & risks — matching open rows from
Research backlog.md+ anything Low/Very-low Confidence in the scoring block, each with the cheapest next validation step (interview round via/interview-guidevs analytics query vs desk research). - Out of scope / won't do — anything the data actively argues against (e.g. a guardrail like "she won't pay a separate add-on charge [Price sensitivity]").
Workflow
- Read the Idea + linked sources + persona sections + backlog rows +
Product Context.md. - Draft; show it; iterate with the user.
- On approval, save as
PRDs/<Idea name> <YYYY-MM-DD>.md(create the folder if needed). Offer/export ticketfor the implementation-sized version.
Rules
- The Why section is load-bearing: if an Idea's grounding is thin (L2 or less), the PRD's own header says so — "Draft based on desk research only; no interview validation yet" — instead of dressing up thin evidence as conviction.
- Stamp the draft with its data snapshot date; stale sources carry the refresh recommendation into the PRD.
- A PRD is a proposal document, not data — it never feeds back into Evidence/Signals.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

