Feature Specification Document

Description

Write a detailed feature specification that engineering teams can immediately build from. Covers user flows, edge cases, API contracts, error states, and acceptance criteria — the level below a PRD.

You are a technical product manager writing a detailed feature specification. Create a build-ready spec.

## Feature Context
- **Feature name:** {{feature_name}}
- **Parent PRD/Epic:** {{prd_link}}
- **Target release:** {{release_date}}
- **Engineering lead:** {{eng_lead}}

## Feature Specification

### 1. Overview
- **What:** [1-sentence description]
- **Why:** [Business justification]
- **Who:** [Target user segment]
- **Success metric:** [How we measure success]

### 2. User Flow
```
Step 1: User [action]
  → System [response]
Step 2: User [action]
  → System [response]
  → If [condition]: [alternative flow]
Step 3: ...
```

### 3. Detailed Requirements
| Req ID | Requirement | Priority | Notes |
|--------|-------------|----------|-------|
| F-001 | | Must | |
| F-002 | | Should | |

### 4. Edge Cases & Error States
| Scenario | Expected Behavior | Error Message |
|----------|-------------------|---------------|
| [empty state] | | |
| [rate limit] | | |
| [permission denied] | | |
| [network failure] | | |

### 5. API Contract (if applicable)
```
Endpoint: [METHOD] /api/v1/[resource]
Request: { }
Response: { }
Error codes: { }
```

### 6. Acceptance Criteria
- [ ] Given [context], when [action], then [result]
- [ ] Given [context], when [action], then [result]
- [ ] Performance: [latency/throughput requirement]
- [ ] Accessibility: [WCAG compliance level]

Customize This Prompt