From prd-builder
Conducts structured PRD interviews across 8 categories including problem context, users, features, tech, business, UX, risks, and testing to build actionable documents with Mermaid diagrams. For features, bug fixes, products, and /prd-builder commands.
npx claudepluginhub mwguerra/claude-code-plugins --plugin prd-builderThis skill uses the workspace's default tool permissions.
Guide comprehensive interviews to transform rough ideas into actionable Product Requirements Documents through structured discovery across 8 categories.
Generates structured Product Requirements Documents (PRDs) by gathering project context from files and commits, asking 3-5 clarifying questions with lettered options, and producing sections like user stories, functional requirements, non-goals, and success metrics.
Generates structured PRDs with problem, context, solution, user stories, acceptance criteria, metrics, risks, and out-of-scope items. Iteratively gathers info via questions, reviews docs/issues/templates.
Share bugs, ideas, or general feedback.
Guide comprehensive interviews to transform rough ideas into actionable Product Requirements Documents through structured discovery across 8 categories.
Conduct interviews across these 8 categories (adapt based on PRD type):
| Category | Focus Areas | When to Use |
|---|---|---|
| Problem & Context | Pain points, current state, why now | Always |
| Users & Customers | Personas, segments, user journeys | Always |
| Solution & Features | Feature list, MVP scope, priorities | Always |
| Technical Implementation | Architecture, stack, integrations | Always |
| Business & Value | ROI, pricing, revenue model | Products, major features |
| UX & Design | Flows, wireframes, accessibility | UI-facing work |
| Risks & Concerns | Dependencies, assumptions, blockers | Always |
| Testing & Quality | Test strategies, acceptance criteria | Always |
When using AskUserQuestion:
Skip categories based on context:
Save interview progress to: .taskmanager/prd-state.json
{
"sessionId": "uuid",
"prdType": "product|feature|bugfix",
"slug": "feature-name",
"startedAt": "ISO timestamp",
"lastUpdatedAt": "ISO timestamp",
"currentCategory": "category-name",
"completedCategories": ["category1", "category2"],
"answers": {
"category-name": {
"question-key": "answer-value"
}
},
"initialPrompt": "User's original description"
}
When /prd-builder:prd or similar is invoked:
.taskmanager/prd-state.jsoncurrentCategorySave PRDs to: docs/prd/prd-{slug}.md
Generate PRDs following the template in templates/prd-template.md. Key sections:
Include these diagrams where appropriate:
Architecture Diagram:
graph TB
subgraph Frontend
UI[User Interface]
end
subgraph Backend
API[API Layer]
DB[(Database)]
end
UI --> API --> DB
User Flow Diagram:
flowchart LR
A[Start] --> B{Decision}
B -->|Yes| C[Action]
B -->|No| D[Alternative]
After PRD completion:
/taskmanager:plan with the PRD file pathFeature: User Authentication
├── Setup authentication infrastructure
├── Implement login endpoint
├── Implement registration endpoint
├── Add password reset flow
├── Create authentication middleware
└── Write authentication tests
After generating tasks, ask: "Tasks created. Start autonomous execution?"
If yes, invoke /taskmanager:run to begin implementation.
/prd-builder:prd)Complete interview covering all 8 categories in depth:
/prd-builder:feature)Lighter interview focused on implementation:
/prd-builder:bugfix)Problem-focused documentation:
/prd-builder:refine)Enhance existing PRDs:
Detailed question banks for each category:
references/question-bank.md - Complete question library organized by categoryPRD output template:
templates/prd-template.md - Full PRD document structure