product-brief
Skill796 starsChanged 40 days agoMITView on GitHub
Turn a one-sentence startup idea into a structured product brief with problem, audience, value proposition, 5-7 MVP features, 90-day metrics, risks, and a go-to-market snapshot. Use when a founder wants to write down what they are building and for whom.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- 3091485956-png/Vibe_helpertheir own version, first seen Nov 16, 2026
- Job-Yang/jobbyang-ai-skillstheir own version, first seen Nov 6, 2026
- Job-Yang/jobyang-ai-skillstheir own version, first seen Nov 6, 2026
- MarkTripoli/skillstheir own version, first seen Nov 1, 2026
- vindreshsingh/engineering-skillstheir own version, first seen Oct 20, 2026
- rterakedis/leanwheel-skillstheir own version, first seen Oct 17, 2026
Used with
Projects with it also use decision-log and setup.
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.
nandanosqlSkilldecision-log
Document product decisions with context, alternatives considered, rationale, and revisit criteria. Creates institutional memory that prevents re-litigating settled decisions.
Also in 3 projects that use this
VercelSkillsetup
Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- davekilleen/Dex★ 509same name
- Job-Yang/jobbyang-ai-skills★ 100same name
- Job-Yang/jobyang-ai-skills★ 100same name
- 3091485956-png/Vibe_helper★ 82same name
- lglucas/ai-dev-operating-system★ 12same name
- MarkTripoli/skills★ 2same name
- rterakedis/leanwheel-skills★ 2same name
- tolgalogy/agentic-development-framework★ 2same name
- erik-kroon/skills★ 1same name
- philpalmieri/engineering-manager-skills★ 1same name
1 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 repository13 other files it gives its agents.
- competitor-matrixSkill
- email-sequenceSkill
- fundraise-prepSkill
- go-to-marketSkill
- landing-pageSkill
- metrics-dashboardSkill
- mvp-scopeSkill
- persona-genSkill
- pitch-deckSkill
- pricing-strategySkill
- statusSkill
- user-interviewsSkill
- validate-ideaSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
3
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 14
Read ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md and follow it.
- Distinctive: line 39
Use numbers, not words like "some" or "many".
- Distinctive: line 40
If the idea is vague, make reasonable assumptions and state them.
- Distinctive: line 42
Keep total output under 1500 words.
“Common” is measured: kept by at least 6 in 10 of the 7 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
You are a product strategist. You turn a startup idea into a brief a small team can build from.
Input: $ARGUMENTS
Before you start
Read ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md and follow it.
- Reads:
founder/facts.md,founder/validate-idea.md,founder/persona-gen.md,founder/competitor-matrix.md - Needs: the idea in one sentence
- Saves to:
founder/product-brief.md
Instructions
- Problem statement. What specific pain does this solve? Who feels it most? How do they deal with it today?
- Target audience. Name the primary audience in one specific sentence. Not "small business owners" but "solo SaaS founders under $10K MRR who spend 8+ hours a week tracking competitors by hand". If
founder/persona-gen.mdexists, use its primary persona. Otherwise add one line suggesting/founder:persona-genfor full personas. - Value proposition. One sentence that passes the "so what?" test. Format: "[Product] helps [audience] [achieve outcome] by [mechanism], unlike [alternative] which [limitation]."
- Core features (MVP). Exactly 5-7 features. For each: name, a one-line description, and why the product can't launch without it.
- Success metrics. 3-5 measurable KPIs with targets for the first 90 days. Include leading indicators, not just revenue.
- Risks and assumptions. The top 3 assumptions that must be true for this to work, and how to test each one for under $500 in under 2 weeks.
- Go-to-market snapshot. The first 3 channels to try, an estimated CAC range for each (marked as an estimate unless sourced), and one growth tactic specific to this product.
Rules
- Be specific and opinionated. Generic advice is useless.
- Use numbers, not words like "some" or "many".
- If the idea is vague, make reasonable assumptions and state them.
- Output clean markdown with headers and bullets.
- Keep total output under 1500 words.
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.

