agentleFS
emotixcoemotixco/claude-skills-founder/skills/product-brief/SKILL.md

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

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

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

  • VercelSkill

    setup

    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

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
  1. Very specific:

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

    line 14
  2. Distinctive:

    Use numbers, not words like "some" or "many".

    line 39
  3. Distinctive:

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

    line 40
  4. Distinctive:

    Keep total output under 1500 words.

    line 42

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.