product-brief — Claude Code skill: what it does, how to install
This Claude Code skill turns a startup concept into a structured product brief. It covers the problem, intended audience, product value, and an initial go-to-market plan.
MIT ★ 900 updated 2026-11-03
npx skills add emotixco/claude-skills-founder --skill product-brief -a claude-codeWhat product-brief does
The skill takes a startup idea in one sentence and writes a brief to founder/product-brief.md. The document sets out the problem and target audience, explains the product’s value, and lists 5–7 MVP features. It also includes 90-day metrics, risks, and an initial go-to-market outline.
Before drafting, it reads ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md along with founder/facts.md, founder/validate-idea.md, founder/persona-gen.md, and founder/competitor-matrix.md. When founder/persona-gen.md is missing, the brief suggests running /founder:persona-gen. The idea itself must be supplied as one sentence.
The output identifies three assumptions and gives a way to test each for under $500 in less than two weeks. It names three initial marketing channels and estimates CAC ranges, labeling them as estimates unless sourced. The brief stays under 1500 words.
What it helps with
- define a startup’s core problem and audience
- outline MVP features and explain their launch relevance
- set measurable targets for the first 90 days
- identify assumptions and low-cost ways to test them
- sketch early marketing channels and estimated CAC
Example prompts for the agent
- Draft a product brief for this idea: a service that helps freelancers manage invoices in one place.
- Define the audience and MVP for an app that simplifies household expense tracking.
- Create a brief for a startup that helps small teams schedule on-call shifts.
How to install product-brief
1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill product-brief -a claude-code2Manually: put the files in place
~/.claude/skills/product-brief/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/product-brief/
1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill product-brief -a codex2Manually: put the files in place
.agents/skills/product-brief/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill product-brief -a cursor2Manually: put the files in place
.cursor/skills/product-brief/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install emotixco/claude-skills-founder skills/product-brief2Manually: put the files in place
.github/skills/product-brief/SKILL.md1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill product-brief -a gemini-cli2Platform CLI
gemini skills install https://github.com/emotixco/claude-skills-founder --path skills/product-briefManually: put the files in place
.devin/skills/product-brief/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill product-brief -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about product-brief
How do I install product-brief in Claude Code?
Run npx skills add emotixco/claude-skills-founder --skill product-brief -a claude-code. The skill is installed at ~/.claude/skills/product-brief/SKILL.md.
What does product-brief do?
It turns a startup concept into a brief covering the problem, audience, product value, MVP features, metrics, risks, and initial marketing channels. The file is saved as founder/product-brief.md.
What does product-brief need to work?
Provide the startup idea as a single sentence. The skill also reads the shared conventions file at ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md and the listed files under founder/.
Source text
SKILL.md · MIT
---
name: product-brief
description: 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.
argument-hint: "[your startup idea in one sentence]"
allowed-tools: Read Edit(founder/**) WebSearch WebFetch
---
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
1. **Problem statement.** What specific pain does this solve? Who feels it most? How do they deal with it today?
2. **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.md` exists, use its primary persona. Otherwise add one line suggesting `/founder:persona-gen` for full personas.
3. **Value proposition.** One sentence that passes the "so what?" test. Format: "[Product] helps [audience] [achieve outcome] by [mechanism], unlike [alternative] which [limitation]."
4. **Core features (MVP).** Exactly 5-7 features. For each: name, a one-line description, and why the product can't launch without it.
5. **Success metrics.** 3-5 measurable KPIs with targets for the first 90 days. Include leading indicators, not just revenue.
6. **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.
7. **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.
© emotixco · MIT · emotixco/claude-skills-founder