Guides you through defining your product MVP by gathering requirements and structuring them into a PRD.
Install
mkdir -p .claude/skills/vibe-prd && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6275" && unzip -o skill.zip -d .claude/skills/vibe-prd && rm skill.zipInstalls to .claude/skills/vibe-prd
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Create a Product Requirements Document (PRD) for your MVP. Use when the user wants to define product requirements, create a PRD, or says "help me write requirements", "create PRD", or "define my product".Key capabilities
- →Guide users through PRD creation
- →Reference existing research documents
- →Tailor requirements to technical skill level
- →Generate structured markdown PRD files
- →Verify product goals and success metrics
How it works
The skill conducts a guided interview to gather product requirements, then synthesizes the information into a structured PRD document based on the user's technical background.
Inputs & outputs
When to use vibe-prd
- →Defining MVP requirements
- →Brainstorming new product features
- →Writing project specification documents
About this skill
Product requirements
Use existing research, the user's request, and Handoff Context to define the product outcome. Do not repeat an interview whose answers are already known. Ask only for unresolved requirements that affect scope or acceptance; make reversible assumptions explicit and continue when the brief is sufficient.
Write a PRD proportional to the product. Cover the target user and problem, the core journey, MVP scope, out-of-scope work, meaningful failure states, constraints, and observable acceptance criteria. Include AI, accounts, payments, analytics, compliance, or automation only when the product needs them.
For a small project, a short document is enough. For a complex one, clarify dependencies and consequential decisions before they block implementation. Avoid fixed feature counts, mandatory personas, or market research that does not change the product decision. Distinguish agreed facts from assumptions.
Use the manifest's configured PRD path or docs/PRD-[AppName]-MVP.md. End with
Handoff Context carrying app, known user level, platform, budget, timeline,
mode, constraints, decisions, source files, and open questions. Do not present
planned acceptance checks as executed evidence. If the user requested the
whole workflow, continue into the technical design within that scope.
For a guided interview with unresolved requirements, consult the relevant optional question prompts.
When producing a document for vibeworkflow, include the exact
CLI output metadata. This is a parser contract,
not an optional prose template.
When not to use it
- →Writing technical design documents
- →Generating code implementations
Limitations
- →Requires user input to define product scope
- →Limited to MVP-focused documentation
How it compares
It maintains session context and adapts the level of detail based on the user's technical proficiency, unlike static templates.
Compared to similar skills
vibe-prd side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| vibe-prd (this skill) | 1 | 5mo | No flags | Beginner |
| pmbok-project-management | 38 | 11mo | No flags | Intermediate |
| project-planner | 32 | 11mo | Review | Intermediate |
| spec-kit-workflow | 11 | 10mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by KhazP
View all by KhazP →You might also like
pmbok-project-management
jgtolentino
Comprehensive PMP/PMBOK project management methodologies and best practices. Use this skill when users need guidance on project management processes, templates, knowledge areas, process groups, tools, techniques, or certification preparation. Covers all 10 PMBOK Knowledge Areas and 5 Process Groups with practical templates, frameworks, and industry-standard approaches. Includes risk management, stakeholder engagement, schedule management, cost control, quality assurance, and resource planning.
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
product-manager-toolkit
davila7
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
planning-agent
parcadei
Planning agent that creates implementation plans and handoffs from conversation context
pdd
mikeyobrien
Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification, research, design, and planning.