prd-builder
Skill1 starsChanged 5 months agoMITView on GitHub
Walks you through a one-page PRD before any code. Fits in a Notion page, prevents 80% of "we built the wrong thing" outcomes. Trigger phrases: PRD, spec out, product requirement, requirements doc, let's plan this feature properly. /prd <feature> — start the flow.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- SayandipBagchi/prd-buildertheir own version, first seen Sep 14, 2026
- BitCrowder/ai-product-dev-skillstheir own version, first seen Jul 26, 2026
- euroconic/pm-claude-skillstheir own version, first seen May 27, 2026
- ZeroPointRepo/CRHQ-PRDstheir own version, first seen May 10, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- ZeroPointRepo/CRHQ-PRDs★ 22same name
- BitCrowder/ai-product-dev-skills★ 1same name
- euroconic/pm-claude-skills★ 0same name
- SayandipBagchi/prd-builder★ 0same name
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 repository12 other files it gives its agents.
- commit-curatorSkill
- context-compactorSkill
- cost-trackerSkill
- decision-recorderSkill
- mcp-finderSkill
- permission-auditorSkill
- prompt-matcherSkill
- pr-reviewerSkill
- repo-onboarderSkill
- scope-clarifierSkill
- skill-matcherSkill
- tdd-flowSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 56
Ask 5 questions in ONE message, not 5 rounds:
“Common” is measured: kept by at least 6 in 10 of the 3 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-builder
Walks you through a one-page PRD before any code. Fits in a Notion page, prevents 80% of "we built the wrong thing" outcomes.
When to activate
Trigger phrases: PRD, spec out, product requirement, requirements doc, let's plan this feature properly.
Output template
# PRD: <Feature Name>
Author: <name> | Date: <YYYY-MM-DD> | Status: draft
## Problem
<2-3 sentences. Whose pain, how often, what they do today.>
## Goal
<one-sentence outcome>
## Non-goals
- <thing we're not doing>
- <thing we're not doing>
## User stories
- As a <user>, I want to <action>, so that <outcome>.
- (3-5 max)
## Solution sketch
<3-5 sentences on the approach. Diagrams optional.>
## Requirements
- Must: <hard requirement>
- Should: <strong preference>
- Won't (v1): <explicit cut>
## Success metrics
- Primary: <quant metric, target>
- Secondary: <quant metric, target>
## Open questions
- <thing we haven't decided>
- <thing we haven't decided>
## Risks
- <risk> → <mitigation>
- <risk> → <mitigation>
## Timeline (rough)
- Week 1: <milestone>
- Week 2: <milestone>Process
- Ask 5 questions in ONE message, not 5 rounds:
- What problem? Whose?
- What's the goal in one sentence?
- What's explicitly out of scope?
- How will you know it worked (metric)?
- What might kill it (risk)?
- Compose the PRD draft
- Ask "anything missing?"
- Save to
docs/prd-<feature-slug>.mdif user agrees - Suggest the natural next skill:
scope-clarifier→tdd-flow→commit-curator
Inputs
- Rough feature idea from the user
- Project context (existing PRDs, recent decisions)
Outputs
- 1-page PRD in markdown
- (optional) Saved file at
docs/prd-<slug>.md
Slash command
/prd <feature> — start the flow.
Why this skill
- 80% of feature failure traces to skipped problem definition
- A 200-word PRD prevents 2000 lines of wrong code
- One-page rule keeps it from becoming "Notion theater"
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.

