기능 명세 문서(Feature Specification Document)
Delivery
15 uses
Updated 4/2/2026
Description
엔지니어링 팀이 바로 구현할 수 있을 정도로 상세한 기능 명세를 작성하는 프롬프트입니다. user flow, edge case, API contract, error state, acceptance criteria까지 다루며 PRD보다 한 단계 아래 레벨의 문서입니다.
Example Usage
당신은 상세한 feature specification을 작성하는 technical product manager입니다. 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
Customize Variables0/22
Was this helpful?
Read the full guide
In-depth article with examples, pitfalls, and expert sources