---
name: product-brief-writer
description: Writes comprehensive product briefs and PRDs. Triggers when user needs to document product requirements, define features, or create product specifications.
title: product-brief-writer
canonical_url: https://skilld.dev/gh/mavric/devenv/product-brief-writer
last_updated: 2026-10-04T00:41:21.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install mavric/devenv/product-brief-writer`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/product-brief-writer`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/mavric/devenv/product-brief-writer) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/product-brief-writer`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/product-brief-writer --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/product-brief-writer --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# 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.
