PRD Creation
Create Product Requirements Documents through structured discovery using Jobs-to-be-Done framework.
Best use case
PRD Creation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create Product Requirements Documents through structured discovery using Jobs-to-be-Done framework.
Teams using PRD Creation should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/prd-creation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How PRD Creation Compares
| Feature / Agent | PRD Creation | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create Product Requirements Documents through structured discovery using Jobs-to-be-Done framework.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# PRD Creation Create Product Requirements Documents through structured discovery using Jobs-to-be-Done framework. ## Agent John (Product Manager) - `bmad-pm-john` ## Workflow 1. Synthesize user interviews and Jobs-to-be-Done analysis 2. Define product goals aligned with business objectives 3. Create detailed feature specifications with acceptance criteria 4. Prioritize using MoSCoW or RICE framework 5. Define MVP scope and release strategy 6. Validate PRD completeness (BMad Master) ## Inputs - `projectName` - Project name - `projectDescription` - Project description - `productBrief` - Product brief from analysis phase (optional) - `complexity` - Project complexity level ## Outputs - PRD with features, user stories, acceptance criteria - Feature prioritization and MVP scope - Non-functional requirements - Validation report ## Process Files - `bmad-orchestrator.js` - Phase 2 of full lifecycle
Related Skills
constitution-creation
Establish project governing principles including dev guidelines, code quality standards, testing policies, UX requirements, performance benchmarks, and security constraints.
Plan Creation
Create a structured task_plan.md with phases, goals, and checkbox tracking for persistent planning.
spec-creation
Feature specification creation from codebase research. Produces requirements, acceptance criteria, architecture decisions, implementation plans, and risk analysis.
Product Brief Creation
Create comprehensive product briefs from market, domain, and technical research.
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.
project-install
Install the Babysitter Codex workspace integration into the current project.