06-product-brief — Claude Code skill: what it does, how to install
06-product-brief drafts a concise product brief before gathering requirements. Helps outline an opportunity and establish how to validate it.
MIT ★ 571 updated 2026-10-29
/plugin marketplace add ai-driven-dev/framework
/plugin install aidd-pm@aidd-frameworkWhat 06-product-brief does
The skill guides you through a clear workflow: defining boundaries (frame), researching and questioning assumptions (discover), optional visual mapping (visualize), drafting the brief (shape), and finalizing the text (finalize).
It keeps evidence, assumptions, and user decisions strictly distinct. Writing to storage requires explicit caller approval. Crucially, this skill stays focused on the opportunity itself and refuses to generate technical requirements, system architecture, or sprint plans.
What it helps with
- frame an early-stage product opportunity before writing specs
- define validation steps and evidence needs for an idea
- isolate unverified assumptions from verified evidence
- align on product scope prior to technical design
Example prompts for the agent
- Help me draft a brief for our new developer tooling idea
- Run 06-product-brief to evaluate this customer feedback pipeline
- Frame an opportunity brief for a local analytics dashboard
How to install 06-product-brief
1Plugin marketplace
/plugin marketplace add ai-driven-dev/framework/plugin install aidd-pm@aidd-frameworkThis installs the whole aidd-pm plugin with all its skills
2Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 06-product-brief -a claude-code3Manually: put the files in place
~/.claude/skills/06-product-brief/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/06-product-brief/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 06-product-brief -a codex2Manually: put the files in place
.agents/skills/06-product-brief/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 06-product-brief -a cursor2Manually: put the files in place
.cursor/skills/06-product-brief/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ai-driven-dev/framework plugins/aidd-pm/skills/06-product-brief2Manually: put the files in place
.github/skills/06-product-brief/SKILL.md1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 06-product-brief -a gemini-cli2Platform CLI
gemini skills install https://github.com/ai-driven-dev/framework --path plugins/aidd-pm/skills/06-product-briefManually: put the files in place
.devin/skills/06-product-brief/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 06-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 06-product-brief
How to install 06-product-brief in Claude Code?
Add the marketplace and install the package by running /plugin marketplace add ai-driven-dev/framework followed by /plugin install aidd-pm@aidd-framework.
What does 06-product-brief do?
It drives a structured interview to evaluate a product concept, challenge assumptions, and assemble a concise brief before engineering work begins.
Can 06-product-brief produce technical specifications?
No, transversal rules prohibit authoring requirements, technical designs, or implementation plans; it strictly frames the product opportunity.
Source text
SKILL.md · MIT
--- name: 06-product-brief description: Produces a concise Product Brief before requirements. Use when the user wants to frame or revisit a product opportunity and how it will be validated. Not for requirements, technical design, or planning. argument-hint: idea | product --- # Product Brief ```mermaid flowchart LR source([idea or product]) --> frame frame --> discover discover -->|"ready or assumptions accepted"| shape discover -->|"visual helps"| visualize visualize -->|"accepted or skipped"| shape shape -->|"evidence gap"| discover shape --> finalize finalize -->|"learn more"| discover finalize -->|"change visual"| visualize finalize -->|"revise brief"| shape finalize -->|"authorized"| done([Product Brief]) ``` ## Actions Run the flow above. Read only the next action file. | Action | Does | | --------- | ------------------------------------ | | frame | establish scope and evidence path | | discover | research, question, and challenge | | visualize | clarify with an optional product view | | shape | compose one Product Brief | | finalize | refine, approve, and persist | ## Transversal rules - Keep product and lifecycle decisions with the user. - Separate evidence, decisions, and assumptions. - Preserve source links and existing edits. - Ask natural questions; never expose actions, references, or unchanged state. - Require explicit approval or caller-provided bounded authority before any write. - Frame the opportunity; never write requirements.
© AI-Driven Dev · MIT · ai-driven-dev/framework