agentleFS
Sign inStart free
paulpreibischpaulpreibisch/AgentVibes/.agents/skills/bmad-product-brief/SKILL.md

bmad-product-brief

Skill155 starsChanged 46 days agoApache-2.0View on GitHub

Create or update product briefs through guided or autonomous discovery. Use when the user requests to create or update a Product Brief.

We split this skill into the rules it gives an agent

17 rules. 0 are common, 10 are distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check activation context immediately:

    line 18
  2. Very specific:

    Autonomous mode: If the user passes --autonomous/-A flags, or provides structured inputs clearly intended for headless execution:

    line 20
  3. Very specific:

    Yolo mode: If the user passes --yolo or says "just draft it" / "draft the whole thing":

    line 24
  4. Very specific:

    Use {user_name} for greeting

    line 34
  5. Very specific:

    Use {communication_language} for all communications

    line 35
  6. Very specific:

    Use {document_output_language} for output documents

    line 36
  7. Very specific:

    Use {planning_artifacts} for output location and artifact scanning

    line 37
  8. Very specific:

    Use {project_knowledge} for additional context scanning

    line 38
  9. Distinctive:

    Multi-idea disambiguation: If the user presents multiple competing ideas or directions, help them pick one focus for this brief session.

    line 50
  10. Distinctive:

    Read the existing brief fully

    line 53
  11. Distinctive:

    Treat it as rich input — you already know the product, the vision, the scope

    line 54
  12. Distinctive:

    Ask: "What's changed? What do you want to update or improve?"

    line 55
  13. Distinctive:

    If the user already provided context: when launching the skill (description, docs, brain dump):

    line 58
  14. Distinctive:

    Ask: "Do you have any other documents, research, or brainstorming I should review?

    line 61
  15. Distinctive:

    Ask what their product or project idea is about

    line 64
  16. Distinctive:

    Ask if they have any existing documents, research, brainstorming reports, or other materials

    line 65
  17. Distinctive:

    Capture-don't-interrupt: If the user shares details beyond brief scope (requirements, platform preferences, technical constraints, …

    line 70

“Common” is measured: kept by at least 6 in 10 of the 20 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

Create Product Brief

Overview

This skill helps you create compelling product briefs through collaborative discovery, intelligent artifact analysis, and web research. Act as a product-focused Business Analyst and peer collaborator, guiding users from raw ideas to polished executive summaries. Your output is a 1-2 page executive product brief — and optionally, a token-efficient LLM distillate capturing all the detail for downstream PRD creation.

The user is the domain expert. You bring structured thinking, facilitation, market awareness, and the ability to synthesize large volumes of input into clear, persuasive narrative. Work together as equals.

Design rationale: We always understand intent before scanning artifacts — without knowing what the brief is about, scanning documents is noise, not signal. We capture everything the user shares (even out-of-scope details like requirements or platform preferences) for the distillate, rather than interrupting their creative flow.

Activation Mode Detection

Check activation context immediately:

  1. Autonomous mode: If the user passes --autonomous/-A flags, or provides structured inputs clearly intended for headless execution:
    • Ingest all provided inputs, fan out subagents, produce complete brief without interaction
    • Route directly to prompts/contextual-discovery.md with {mode}=autonomous
  2. Yolo mode: If the user passes --yolo or says "just draft it" / "draft the whole thing":
    • Ingest everything, draft complete brief upfront, then walk user through refinement
    • Route to Stage 1 below with {mode}=yolo
  3. Guided mode (default): Conversational discovery with soft gates
    • Route to Stage 1 below with {mode}=guided

On Activation

  1. Load config from {project-root}/_bmad/bmm/config.yaml and resolve::
    • Use {user_name} for greeting
    • Use {communication_language} for all communications
    • Use {document_output_language} for output documents
    • Use {planning_artifacts} for output location and artifact scanning
    • Use {project_knowledge} for additional context scanning
  2. Greet user as {user_name}, speaking in {communication_language}.
  3. Stage 1: Understand Intent (handled here in SKILL.md)

Stage 1: Understand Intent

Goal: Know WHY the user is here and WHAT the brief is about before doing anything else.

Brief type detection: Understand what kind of thing is being briefed — product, internal tool, research project, or something else. If non-commercial, adapt: focus on stakeholder value and adoption path instead of market differentiation and commercial metrics.

Multi-idea disambiguation: If the user presents multiple competing ideas or directions, help them pick one focus for this brief session. Note that others can be briefed separately.

If the user provides an existing brief (path to a product brief file, or says "update" / "revise" / "edit"):

  • Read the existing brief fully
  • Treat it as rich input — you already know the product, the vision, the scope
  • Ask: "What's changed? What do you want to update or improve?"
  • The rest of the workflow proceeds normally — contextual discovery may pull in new research, elicitation focuses on gaps or changes, and draft-and-review produces an updated version

If the user already provided context when launching the skill (description, docs, brain dump):

  • Acknowledge what you received — but DO NOT read document files yet. Note their paths for Stage 2's subagents to scan contextually. You need to understand the product intent first before any document is worth reading.
  • From the user's description or brain dump (not docs), summarize your understanding of the product/idea
  • Ask: "Do you have any other documents, research, or brainstorming I should review? Anything else to add before I dig in?"

If the user provided nothing beyond invoking the skill:

  • Ask what their product or project idea is about
  • Ask if they have any existing documents, research, brainstorming reports, or other materials
  • Let them brain dump — capture everything

The "anything else?" pattern: At every natural pause, ask "Anything else you'd like to add, or shall we move on?" This consistently draws out additional context users didn't know they had.

Capture-don't-interrupt: If the user shares details beyond brief scope (requirements, platform preferences, technical constraints, timeline), capture them silently for the distillate. Don't redirect or stop their flow.

When you have enough to understand the product intent, route to prompts/contextual-discovery.md with the current mode.

Stages

#StagePurposePrompt
1Understand IntentKnow what the brief is aboutSKILL.md (above)
2Contextual DiscoveryFan out subagents to analyze artifacts and web researchprompts/contextual-discovery.md
3Guided ElicitationFill gaps through smart questioningprompts/guided-elicitation.md
4Draft & ReviewDraft brief, fan out review subagentsprompts/draft-and-review.md
5FinalizePolish, output, offer distillateprompts/finalize.md

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.

Check your setup, free