From vk
Generate a PRD from a project idea through guided questions
How this skill is triggered — by the user, by Claude, or both
Slash command
/vk:generate-prdThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are helping the user create a structured Product Requirements Document (PRD) from a high-level project idea. You will conduct a brief interview to gather the information needed, then generate a complete PRD.
You are helping the user create a structured Product Requirements Document (PRD) from a high-level project idea. You will conduct a brief interview to gather the information needed, then generate a complete PRD.
If the user provided an idea inline (e.g., /vk:generate-prd build a recipe sharing app), use that as the starting point. Otherwise, ask:
What's your project idea? Give me a brief description of what you want to build.
Use the AskUserQuestion tool to gather requirements interactively. Ask up to 4 questions per round, grouped by topic. Skip questions the user already answered. Adapt questions based on the project type.
Round 1 - Scope & Users (use AskUserQuestion):
Suggested questions (adapt to project):
multiSelect: true with common exclusions like: Mobile app / Admin panel / Analytics / IntegrationsRound 2 - Technical & Constraints (use AskUserQuestion):
Round 3 - Success & Delivery (use AskUserQuestion):
multiSelect: true with: External APIs / Other teams / Third-party services / NoneOpen-ended follow-ups: After the interactive rounds, output any remaining open-ended questions as plain markdown for the user to answer freely (e.g., "Describe any specific technical constraints not covered above").
If the user gives short answers or picks defaults, that's fine — fill in reasonable defaults and flag assumptions.
Write the PRD to docs/prd.md. If the file already exists, warn the user and ask before overwriting.
Use this format:
# PRD: [Project Name]
> **Author:** [User]
> **Created:** [date]
> **Status:** Draft
## Problem Statement
[What problem does this solve? Why does it matter?]
## Goals
1. [Primary goal]
2. [Secondary goal]
3. [Tertiary goal]
## Non-Goals (Out of Scope)
- [Explicitly excluded item 1]
- [Explicitly excluded item 2]
## Target Users / Personas
### Persona 1: [Name/Role]
- **Description:** [Who they are]
- **Needs:** [What they need from this product]
- **Pain points:** [Current frustrations]
### Persona 2: [Name/Role]
- **Description:** [Who they are]
- **Needs:** [What they need]
- **Pain points:** [Current frustrations]
## Functional Requirements
### FR-1: [Feature Area]
- [Requirement 1.1]
- [Requirement 1.2]
### FR-2: [Feature Area]
- [Requirement 2.1]
- [Requirement 2.2]
### FR-3: [Feature Area]
- [Requirement 3.1]
## Non-Functional Requirements
- **Performance:** [Response times, throughput]
- **Scalability:** [Expected load, growth]
- **Security:** [Auth, data protection]
- **Reliability:** [Uptime, error handling]
- **Accessibility:** [Standards, compliance]
## Tech Stack (Suggested)
- **Backend:** [technologies]
- **Frontend:** [technologies]
- **Database:** [technologies]
- **Infrastructure:** [hosting, CI/CD]
## Success Metrics
| Metric | Target | How Measured |
|--------|--------|--------------|
| [Metric 1] | [Target value] | [Measurement method] |
| [Metric 2] | [Target value] | [Measurement method] |
## Dependencies
- [External dependency 1]
- [External dependency 2]
## Risks & Open Questions
| Risk/Question | Impact | Mitigation/Answer |
|---------------|--------|-------------------|
| [Risk 1] | [High/Medium/Low] | [Mitigation strategy] |
| [Open question 1] | [High/Medium/Low] | [TBD] |
## Timeline / Milestones
| Milestone | Target Date | Description |
|-----------|-------------|-------------|
| MVP | [date] | [What's included] |
| V1.0 | [date] | [What's included] |
After generating, list any assumptions you made where the user didn't provide specifics. For example:
Assumptions made (please verify):
- Assumed web-based (not mobile native)
- Assumed PostgreSQL for database
- Assumed single-tenant for MVP
After creating the PRD, inform the user:
docs/prd.md/vk:prd-review for a structured review and gap analysis/vk:create-plan to generate a development plan with epics and tasksGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub materemias/claude-vibekanban-plugin --plugin vk