# Product Brief Writer

> Writes comprehensive product briefs and PRDs. Triggers when user needs to document product requirements, define features, or create product specifications.

- Skill: `majiayu000/product-brief-writer` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add majiayu000/product-brief-writer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/product-brief-writer/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/product-brief-writer

---


# Product Brief Writer

I create structured, comprehensive Product Requirement Documents (PRDs) that serve as the foundation for your project.

## What I Create

A complete PRD with:

### 1. Problem Statement
- Clear articulation of the problem
- Why this problem matters
- Current alternatives and their shortcomings
- Opportunity size

### 2. Target Users & Personas
- Primary user persona (detailed)
- Secondary personas (if applicable)
- User pain points and goals
- User journey maps

### 3. Product Vision
- Core value proposition
- Success criteria
- Competitive differentiation
- Long-term vision (1-3 years)

### 4. MVP Feature Set
- Must-have features (with rationale)
- Feature prioritization
- What's explicitly NOT in MVP (and why)
- Success metrics for each feature

### 5. User Stories
For each major feature:
```
As a [user type]
I want to [action]
So that [benefit]

Acceptance Criteria:
- [ ] Criterion 1
- [ ] Criterion 2
```

### 6. Technical Considerations
- Integration requirements
- Performance requirements
- Security requirements
- Scalability needs
- Data compliance (GDPR, etc.)

### 7. Success Metrics
- Key Performance Indicators (KPIs)
- Target metrics for MVP
- How you'll measure success
- User validation strategy

### 8. Timeline & Milestones
- MVP timeline
- Major milestones
- Dependencies
- Risk factors

### 9. Post-MVP Roadmap
- Features for v2, v3
- Scaling considerations
- Enterprise features

## How I Work

### Input I Need From You

**Minimum:**
- What are you building? (2-3 sentences)
- Who will use it?
- What problem does it solve?

**Ideal:**
- Detailed problem description
- User research insights
- Competitive analysis
- Business model
- Success criteria

### My Process

1. **Discovery Questions** - I'll ask clarifying questions
2. **Structure Creation** - I'll organize information into PRD format
3. **Gap Analysis** - I'll identify missing information
4. **Draft Generation** - I'll write the complete PRD
5. **Iteration** - We'll refine based on your feedback

### Output Format

Markdown file saved to `features/docs/product-requirements.md` with:
- Clear section headers
- Bullet points for scannability
- Tables for comparisons
- User story cards
- Metric definitions

## Best Practices I Follow

✅ **User-Centric** - Every feature tied to user needs
✅ **Measurable** - Clear success criteria
✅ **Prioritized** - Features ranked by importance
✅ **Realistic** - Scope appropriate for timeline
✅ **Actionable** - Clear enough for engineers to implement

## When to Use Me

- ✅ Starting a new product
- ✅ Need to document existing product
- ✅ Pitching to stakeholders/investors
- ✅ Aligning team on vision
- ✅ Before starting development

## Example Output Structure

```markdown
# [Product Name] - Product Requirements Document

## 1. Executive Summary
[2-3 paragraph overview]

## 2. Problem Statement
[Detailed problem description]

## 3. Target Users
### Primary Persona: [Name]
- Demographics: ...
- Pain Points: ...
- Goals: ...

## 4. Product Vision
[Vision statement and differentiation]

## 5. MVP Feature Set

### Feature 1: [Name]
**Priority:** Must-Have
**User Story:** As a [user], I want to [action] so that [benefit]
**Why Critical:** [Rationale]
**Success Metric:** [How we measure success]
**Acceptance Criteria:**
- [ ] Criterion 1
- [ ] Criterion 2

[Repeat for each feature]

## 6. Non-Goals (Out of Scope for MVP)
- Feature X - Why: [reason]
- Feature Y - Why: [reason]

## 7. Technical Requirements
[Integration needs, performance, security, scalability]

## 8. Success Metrics
| Metric | Target | Timeline |
|--------|--------|----------|
| Active Users | 100 | Week 12 |
| Conversion Rate | 20% | Week 12 |

## 9. Timeline
- Week 1-2: Foundation
- Week 3-6: Core features
- Week 7-9: Polish
- Week 10-12: Launch prep

## 10. Risks & Mitigation
[Key risks and how to address them]

## 11. Post-MVP Roadmap
[v2, v3 features]
```

## Ready to Start?

Tell me about what you're building, and I'll create a comprehensive PRD that will guide your development.