Prd
Use when starting a new feature, defining requirements, or formalizing specifications from a rough task description.From its SKILL.md
npx -y skills add junielton/claude-base-dtk --skill prdAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.6 KB, as published. Nobody here has run it
PRD Generator
Transform a rough task description into a well-structured PRD through interactive refinement.
Input
Read and analyze: $ARGUMENTS
If no file is provided, ask the user to describe the feature.
Process — Interactive Refinement
Do NOT generate immediately. First analyze, then refine.
Step 1: Initial Analysis
- Summary of what you understood
- Confidence level (low/medium/high)
- Gaps and ambiguities identified
Step 2: Clarifying Questions (max 5-7, max 3 rounds)
- Scope & Goals: problem, beneficiaries, business value
- User Experience: expected flow, UI/UX
- Edge Cases: failures, empty states, concurrency
- Technical Constraints: performance, APIs, migrations
- Dependencies: other features/systems affected
- Out of Scope: what's explicitly excluded
Step 3: Confirm
"Should I generate the PRD now, or is there anything else to add?"
Output
Save to docs/prds/PRD-{short-kebab-title}.md
Template
# PRD: {Feature Title}
> **Status:** Draft
> **Author:** {Developer name if known}
> **Created:** {Date}
> **Last Updated:** {Date}
---
## 1. Overview
### 1.1 Summary
{2-3 sentences: core goal, who benefits}
### 1.2 Problem Statement
{What problem, why it matters}
---
## 2. User Stories
- As a {user}, I want {action} so that {benefit}
- ...
---
## 3. Functional Requirements
### 3.1 Acceptance Criteria
- [ ] AC1: Given {context}, When {action}, Then {result}
- [ ] AC2: ...
### 3.2 Business Rules
{Validation rules, constraints}
---
## 4. User Experience
### 4.1 User Flow
{Step-by-step interaction}
### 4.2 UI/UX Considerations
{Components, responsive behavior, accessibility}
---
## 5. Technical Approach
### 5.1 Architecture & Design
{Patterns, component structure}
### 5.2 Data Model
{Tables, columns, migrations}
### 5.3 API Contracts
{Endpoints, request/response, status codes}
### 5.4 Dependencies
{External services, packages}
---
## 6. Edge Cases & Error Handling
| Scenario | Expected Behavior |
|----------|-------------------|
| ... | ... |
---
## 7. Testing Strategy
### 7.1 Unit Tests
### 7.2 Feature/Integration Tests
### 7.3 Manual Testing Checklist
- [ ] ...
---
## 8. Out of Scope
- ...
---
## 9. Open Questions
- ...
---
## 10. References
- ...
Rules
- Write in English
- Acceptance criteria must be testable
- Tailor to project's stack (check CLAUDE.md)
- Omit empty sections for simple features
- PRDs live in
docs/prds/— version-controlled, permanent