agentskills.codes
PR

product-brief

Create a product brief with structured process, quality checks, and system integration

Install

mkdir -p .claude/skills/product-brief-datbeat && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16847" && unzip -o skill.zip -d .claude/skills/product-brief-datbeat && rm skill.zip

Installs to .claude/skills/product-brief-datbeat

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 integration
86 charsno explicit “when” trigger

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.md for current project context and priorities
  • Check knowledge-base.md for relevant learned rules or constraints
  • Review any existing related documents in the project
  • Note any active tasks in Task Board.md that 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.md if 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

Search skills

Search the agent skills registry