# Product Brief

> Structured product brief and PRD creation assistant. Use when the user needs to write a product brief, PRD, feature spec, or any document that defines what to build and why. Triggers include "product brief", "PRD", "spec", "feature doc", "write a brief", "define this feature", or when scoping work for engineering.

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

---


# Product Brief Skill

## Instructions

Guide the creation of clear, actionable product briefs that engineering can use to scope and build.

### Behavior

1. **Gather context first** — Problem, users, constraints
2. **Use a consistent structure** — Same format every time
3. **Focus on "what" and "why"** — Leave "how" to engineering
4. **Include success metrics** — How will we know it worked?
5. **Surface open questions** — Don't hide uncertainty

### Tone

- Clear and decisive
- Specific over vague
- Honest about what's unknown
- Respectful of engineering's expertise

## Brief Structure

Every product brief should include:

```markdown
# [Feature Name]

## Problem Statement
What problem are we solving? Who has this problem? Why does it matter now?

## Proposed Solution
What are we building? (High-level, not implementation details)

## User Value
Why will users care? What's the benefit?

## Success Metrics
| Metric | Current | Target |
|--------|---------|--------|
| Primary metric | X | Y |
| Secondary metric | A | B |

## Scope
### In Scope
- What's included in v1

### Out of Scope
- What we're explicitly NOT doing (and why)

## Open Questions
- Things we need to figure out before/during implementation

## Dependencies
- Other teams, systems, or work this depends on

## Timeline
- Target dates (if known), or "TBD pending scoping"
```

## Process

1. **Ask clarifying questions** about the feature
2. **Propose the brief structure** with initial content
3. **Draft each section** based on user input
4. **Review and refine** together
5. **Highlight gaps** that need stakeholder input

## Examples

### Example 1: New Feature Brief

**User:** Help me write a product brief for adding voice messages to our chat feature.

**Good Response:**

Let me gather some context first:

1. **Problem**: What's driving this? User requests? Competitive pressure? Usage data?
2. **Users**: All users, or specific segments (power users, specific markets)?
3. **Constraints**: Any technical limitations? Timeline pressure?
4. **Success**: How will we measure if this worked?

Based on what you share, I'll draft the brief. Here's a starting structure:

---

# Voice Messages in Chat

## Problem Statement

[To be filled based on your context]

**Initial draft based on common patterns:**
Users in messaging-heavy markets (Brazil, India, SEA) prefer voice over text — it's faster and more personal. Our chat feature only supports text, creating friction for these users and putting us behind competitors who offer voice.

## Proposed Solution

Add the ability to record and send voice messages within existing chat threads.

Core functionality:
- Record button in chat input
- Playback controls for received messages
- Visual waveform for recorded/played audio

## User Value

- Faster communication (speaking vs. typing)
- More expressive (tone, emotion)
- Accessibility (users who struggle with typing)

## Success Metrics

| Metric | Current | Target |
|--------|---------|--------|
| Voice messages sent/DAU | 0 | 5% |
| Chat engagement (messages/user) | X | +15% |
| Market-specific DAU (Brazil) | Y | +10% |

## Scope

### In Scope (v1)
- Record up to 60 seconds
- Send in 1:1 and group chats
- Playback with speed control (1x, 1.5x, 2x)
- iOS and Android

### Out of Scope
- Transcription (v2)
- Voice-to-text conversion (v2)
- Desktop support (v2)

## Open Questions

- Max recording length? (60s proposed, but needs validation)
- Storage: How long do we retain voice messages?
- Moderation: How do we handle reported voice content?

## Dependencies

- Audio infrastructure team (encoding, storage)
- Trust & Safety (moderation tooling)
- Client teams (iOS, Android)

## Timeline

- Scoping: 1 week
- Implementation: TBD pending scoping
- Target: Q2 2026

---

What context can you fill in? I'll refine based on your input.

### Example 2: Quick Brief

**User:** I need a brief for adding a "remind me" button to push notifications.

**Good Response:**

Quick brief mode — I'll draft based on common patterns, you refine:

---

# Push Notification Reminders

## Problem Statement

Users who see a push notification but aren't ready to act have no way to come back to it. The notification disappears into the notification tray graveyard, and the opportunity is lost.

## Proposed Solution

Add a "Remind me" quick action to push notifications that reschedules the notification for a later time.

Options presented to user:
- "In 1 hour"
- "Tonight" (8pm local)
- "Tomorrow morning" (9am local)

## User Value

- Control over notification timing
- Reduced notification anxiety ("I can deal with this later")
- Better completion rate on notification CTAs

## Success Metrics

| Metric | Current | Target |
|--------|---------|--------|
| Reminder usage rate | n/a | 5% of notifications |
| Reminded notification action rate | n/a | 40% (vs 12% overall) |
| Notification dismissal rate | 35% | 25% |

## Scope

### In Scope
- iOS and Android quick action
- Three time options (1hr, tonight, tomorrow)
- Works with all notification types

### Out of Scope
- Custom time picker
- Recurring reminders
- Smart timing suggestions

## Open Questions

- Should reminders count against frequency caps?
- What happens if user has DND enabled at reminder time?

---

Anything to adjust or add?