メニュー
This skill should be used when the user asks to "create a PRD", "write requirements", "document a feature", "generate product spec", "define requirements", "write feature specifications", or when creating PRD documents from gathered requirements.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
| name | prd-template |
| description | This skill should be used when the user asks to "create a PRD", "write requirements", "document a feature", "generate product spec", "define requirements", "write feature specifications", or when creating PRD documents from gathered requirements. |
| version | 0.1.0 |
Create well-structured Product Requirements Documents following industry best practices.
A comprehensive PRD includes these sections:
## 1. Overview
### 1.1 Problem Statement
[2-3 sentences describing the problem users face]
### 1.2 Proposed Solution
[High-level description of what we're building]
### 1.3 Target Users
[Who will use this feature and their characteristics]
### 1.4 Success Metrics
- [Measurable metric 1]
- [Measurable metric 2]
Organize requirements with consistent IDs and categories:
## 2. Requirements
### 2.1 Core Features
**REQ-001: [Requirement Title]**
- Description: The system shall [specific, testable behavior]
- Priority: High
- Rationale: [Why this matters]
**REQ-002: [Requirement Title]**
- Description: The system shall [specific, testable behavior]
- Priority: High
- Rationale: [Why this matters]
### 2.2 User Interface
**REQ-010: [UI Requirement]**
- Description: [Specific UI behavior]
- Priority: Medium
### 2.3 Data & Storage
**REQ-020: [Data Requirement]**
- Description: [Data handling behavior]
- Priority: High
Requirement Categories:
## 3. User Stories
### 3.1 Primary Flow
As a [user type], I want to [goal] so that [benefit].
**Acceptance Criteria:**
- Given [context], when [action], then [result]
- Given [context], when [action], then [result]
### 3.2 [Secondary Flow]
As a [user type], I want to [goal] so that [benefit].
## 4. Technical Considerations
### 4.1 Constraints
- [Technical constraint 1]
- [Technical constraint 2]
### 4.2 Dependencies
- [Dependency on system X]
- [Dependency on team Y]
### 4.3 Known Technical Debt
- [Relevant existing debt that affects this feature]
## 5. Out of Scope
The following are explicitly NOT included in this version:
- [Feature X] - Deferred to v2
- [Feature Y] - Requires separate initiative
- [Feature Z] - Out of product scope
## 6. Open Questions
1. [Question requiring stakeholder input]
- Options: A, B, C
- Recommendation: [if any]
2. [Technical question]
- Blocked by: [dependency]
Before finalizing a PRD, verify:
Vague requirements:
Specific requirements:
Solution-focused:
Problem-focused:
For a complete PRD example, see examples/sample-prd.md.
SOC 職業分類に基づく
This skill should be used when the user asks to "generate tasks", "create implementation plan", "break down feature", "write agent prompts", "decompose into tasks", "create work items", or when creating agent-ready task descriptions from PRD and SDD documents.
Verify the current task and output a completion marker. Use this to check if a task is complete and signal the stop hook to allow session exit.
This skill should be used when the user asks to "analyze the codebase", "understand the tech stack", "extract project patterns", "get codebase context", "what technologies are used", or when preparing context for planning documents, PRDs, or design documentation.
This skill should be used when the user asks to "research documentation", "find framework docs", "search for best practices", "look up API documentation", "find implementation patterns", "research how to implement", or when gathering external technical knowledge to inform planning or design decisions.
This skill should be used when the user asks to "create a design document", "write technical specs", "document architecture", "generate SDD", "design the system", "API design", or when creating technical design documents from approved PRDs.
