product-brief
A structured framework for creating professional product briefs that include success metrics and stakeholder requirements.
Install
mkdir -p .claude/skills/product-brief && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16846" && unzip -o skill.zip -d .claude/skills/product-brief && rm skill.zipInstalls to .claude/skills/product-brief
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Create a product brief with structured process, quality checks, and system integrationKey capabilities
- →Review existing product brief documents
- →Identify key stakeholders and their requirements
- →Select appropriate product management frameworks
- →Apply frameworks to structure the brief
- →Define success metrics for the product or feature
- →Document assumptions and dependencies
How it works
This skill follows a four-step process: context and research, analysis and framework application, building the deliverable, and quality validation, to create a product brief.
Inputs & outputs
When to use product-brief
- →Creating a feature specification
- →Defining success metrics for a launch
- →Analyzing user requirements for a brief
- →Documenting product goals
About this skill
Product Brief
Purpose
Create a comprehensive product brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time.
Category: Product Management
Inputs
Required
- Objective: What you want to achieve with this deliverable
- Product/Feature: What product or feature this relates to
Optional
- User Research: Existing insights or data
- Constraints: Technical, timeline, or resource limitations
System Context
Before starting:
- Read
memory.mdfor current project context and priorities - Check
knowledge-base.mdfor relevant learned rules or constraints - Review any existing related documents in the project
- Note any active tasks in
Task Board.mdthat relate to this deliverable
Process
Step 1: Context & Research
- Review any existing product brief documents in the project
- Check knowledge-base.md for relevant learned rules or constraints
- Check memory.md for current project context and priorities
- Identify key stakeholders and their requirements
- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring
Step 2: Analysis & Framework Application
- Apply the selected framework to structure the product brief
- Identify gaps, opportunities, and risks
- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30)
- Document assumptions and dependencies
- Validate approach against industry best practices
Step 3: Build the Deliverable
- Structure the product brief using the output format below
- Include specific, actionable recommendations — not generic advice
- Add concrete numbers, timelines, and benchmarks where applicable
- Cross-reference with existing project documents for consistency
- Ensure every section adds value — remove filler
Step 4: Quality Validation
- All required inputs have been addressed
- Recommendations are specific and actionable (not vague)
- Numbers and benchmarks are realistic and sourced
- Output format matches the specification below
- No contradictions with knowledge-base rules
- Follows best practice: Talk to 5 users before building anything
Output Format
# Product Brief
## Executive Summary
[2-3 sentence overview of the deliverable and key recommendations]
## Context & Objectives
- **Objective**: [What this achieves]
- **Audience**: [Who this is for]
- **Timeline**: [When this applies]
## Analysis
[Structured analysis using the selected framework]
## Recommendations
1. [Specific, actionable recommendation with expected impact]
2. [Specific, actionable recommendation with expected impact]
3. [Specific, actionable recommendation with expected impact]
## Implementation
| Action | Owner | Timeline | Priority |
|--------|-------|----------|----------|
| [Action item] | [Who] | [When] | [High/Medium/Low] |
## Success Metrics
| Metric | Current | Target | Measurement Method |
|--------|---------|--------|-------------------|
| [KPI] | [Baseline] | [Goal] | [How to measure] |
## Risks & Mitigations
| Risk | Likelihood | Impact | Mitigation |
|------|-----------|--------|------------|
| [Risk] | [H/M/L] | [H/M/L] | [Action] |
## Next Steps
- [ ] [Immediate next action]
- [ ] [Follow-up action]
- [ ] [Review date]
Applicable Frameworks
- Jobs To Be Done
- Kano Model
- RICE Scoring
- MoSCoW Prioritization
- Double Diamond
- Build-Measure-Learn
- Product-Led Growth
- AARRR (Pirate Metrics)
Key Metrics
- Activation Rate
- Feature Adoption
- Daily/Monthly Active Users
- Retention (D1/D7/D30)
- Net Revenue Retention
- Time to Value
- Customer Effort Score
Best Practices
- Talk to 5 users before building anything
- One metric that matters per quarter
- Ship small and iterate — 2-week max cycles
- Always define success criteria before building
- Kill features that less than 10% of users use
After Completion
- Update
memory.mdif this deliverable changes project context or priorities - Add any reusable learnings to
knowledge-nominations.md - If follow-up actions were identified, add them to
Task Board.md - Recommend related skills if additional work is needed
When not to use it
- →When the objective is not to create a complete product brief
- →When the user does not want to follow a structured process with quality validation
- →When the task is not related to product management
Limitations
- →Requires an objective and product/feature as input
- →Relies on existing `memory.md`, `knowledge-base.md`, and `Task Board.md` for context
- →Mandates specific output format and quality validation steps
How it compares
This process integrates specific product management frameworks and quality checks, ensuring a professional-grade output with actionable recommendations, unlike a generic document creation.
Compared to similar skills
product-brief side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| product-brief (this skill) | 0 | 3mo | No flags | Intermediate |
| bmad-agent-pm | 0 | 1mo | No flags | Intermediate |
| spec-kit-workflow | 11 | 8mo | No flags | Intermediate |
| product-manager-toolkit | 32 | 8mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by DatBeat
View all by DatBeat →You might also like
bmad-agent-pm
alibaba
Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
product-manager-toolkit
davila7
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
f2s-req-clarify
Lands-1203
针对 PRD/需求反问直到清楚,再可用 f2s-req-tech 出技术方案;触发:需求澄清、PRD 澄清
self-host-development-light
doolin
Lightweight self-hosted project management using markdown files in a .development directory. Covers backlog, planning, todo, roadmap, and saved plans — everything an agent needs to orient and start working.
to-prd
manuelseeger
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.