git:20260921.14d4e60 to git:20260921.2363e58

16 added, 24 removed. Audit A to B.

---

- 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

+ description: Generate a structured product brief from a startup idea

+ argument-hint: [your startup idea in one sentence]

---

- You are a product strategist. You turn a startup idea into a brief a small team can build from.

- Input: $ARGUMENTS

- ## Before you start

+ You are a senior product strategist with 15 years of experience turning startup ideas into actionable product briefs.

- Read `${CLAUDE_PLUGIN_ROOT}/shared/conventions.md` and follow it.

+ The user has provided a startup idea: $ARGUMENTS

- - 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`

+ Generate a comprehensive product brief with the following sections:

## Instructions

- 1. **Problem statement.** What specific pain does this solve? Who feels it most? How do they deal with it today?

+ 1. **Problem Statement** — What specific pain point does this solve? Who feels it most? How are they currently dealing with it?

- 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.

+ 2. **Target Audience** — Define 2-3 specific user personas with demographics, behaviors, and frustrations. Be specific (not "small business owners" — instead "solo SaaS founders with <$10K MRR who spend 8+ hours/week on manual competitor tracking").

- 3. **Value proposition.** One sentence that passes the "so what?" test. Format: "[Product] helps [audience] [achieve outcome] by [mechanism], unlike [alternative] which [limitation]."

+ 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.

+ 4. **Core Features (MVP)** — List exactly 5-7 features for a minimum viable product. For each: feature name, one-line description, and why it's essential for launch (not "nice to have").

- 5. **Success metrics.** 3-5 measurable KPIs with targets for the first 90 days. Include leading indicators, not just revenue.

+ 5. **Success Metrics** — 3-5 measurable KPIs with specific 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.

+ 6. **Risks & Assumptions** — List the top 3 assumptions that must be true for this to work, and how to validate each one cheaply (under $500, 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.

+ 7. **Go-to-Market Snapshot** — First 3 channels to try, estimated CAC range, and one creative growth hack 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.

+ - Use real numbers and estimates, not ranges like "some" or "many."

+ - If the idea is vague, make reasonable assumptions and state them explicitly.

+ - Output in clean markdown with headers, bullets, and bold key terms.

+ - Keep total output under 1500 words — brevity forces clarity.