project-docs

# Project Documentation Skill

Patterns and templates for creating project briefs and product requirements documents (PRDs).

## Purpose

Create **non-technical** project documentation that answers:
- **What** is this project?
- **Who** is it for?
- **Why** does it exist?
- **What problem** does it solve?

This is NOT technical documentation. For technical docs, use CLAUDE.md.

## Project Brief vs PRD vs CLAUDE.md

| Document | Purpose | Audience |
|----------|---------|----------|
| project.md | Project identity and goals | Stakeholders, team |
| brand.md | Visual and verbal identity | Designers, marketing |
| CLAUDE.md | Technical configuration | Claude Code |

## Project.md Structure

### Minimal (MVP/Side Projects)

```markdown
# [Project Name]

> [Tagline - one memorable sentence]

[2-3 sentence description]

## Problem

[What pain point does this solve?]

## Solution

[How does your project solve it?]

## Target User

[Who is this for?]
```

### Standard (Startups/Products)

```markdown
# [Project Name]

> [Tagline]

[Description]

## Problem

**What**: [The pain point]
**Who**: [Who experiences it]
**Impact**: [Cost of the problem]

## Solution

[Value proposition]

## Target Audience

**Primary User**: [Role and context]
- Technical level: [Level]
- Key goal: [What they want]

## Core Features

| Feature | Benefit |
|---------|---------|
| [Name] | [User value] |

## Success Metrics

| Metric | Target | Timeframe |
|--------|--------|-----------|
| [KPI] | [Goal] | [When] |
```

### Comprehensive (Enterprise/Funded)

```markdown
# [Project Name]

> [Tagline]

[Description]

## Executive Summary

[One paragraph overview for executives]

## Problem Statement

**Problem**: [Detailed pain point]
**Evidence**: [Data, research, quotes]
**Who**: [Target segment with size]
**Impact**: [Business cost if unsolved]

## Solution

**Value Proposition**:
For [TARGET USER]
who [NEED/PROBLEM],
[PROJECT NAME] is a [CATEGORY]
that [KEY BENEFIT].
Unlike [ALTERNATIVES],
we [UNI