create-prd
Create a PRD from scratch. Use when the user says "lets create a product requirements document" or "I want to create a new PRD"
Install
mkdir -p .claude/skills/create-prd-ashendulsanka && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17047" && unzip -o skill.zip -d .claude/skills/create-prd-ashendulsanka && rm skill.zipInstalls to .claude/skills/create-prd-ashendulsanka
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 PRD from scratch. Use when the user says "lets create a product requirements document" or "I want to create a new PRD"About this skill
PRD Create Workflow
Goal: Create comprehensive PRDs through structured workflow facilitation.
Your Role: Product-focused PM facilitator collaborating with an expert peer.
You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
Conventions
- Bare paths (e.g.
steps-c/step-01-init.md) resolve from the skill root. {skill-root}resolves to this skill's installed directory.{project-root}-prefixed paths resolve from the project working directory.
WORKFLOW ARCHITECTURE
This uses step-file architecture for disciplined execution:
Core Principles
- Micro-file Design: Each step is a self-contained instruction file that is a part of an overall workflow that must be followed exactly
- Just-In-Time Loading: Only the current step file is in memory - never load future step files until told to do so
- Sequential Enforcement: Sequence within the step files must be completed in order, no skipping or optimization allowed
- State Tracking: Document progress in output file frontmatter using
stepsCompletedarray when a workflow produces a document - Append-Only Building: Build documents by appending content as directed to the output file
Step Processing Rules
- READ COMPLETELY: Always read the entire step file before taking any action
- FOLLOW SEQUENCE: Execute all numbered sections in order, never deviate
- WAIT FOR INPUT: If a menu is presented, halt and wait for user selection
- CHECK CONTINUATION: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
- SAVE STATE: Update
stepsCompletedin frontmatter before loading next step - LOAD NEXT: When directed, read fully and follow the next step file
Critical Rules (NO EXCEPTIONS)
- 🛑 NEVER load multiple step files simultaneously
- 📖 ALWAYS read entire step file before execution
- 🚫 NEVER skip steps or optimize the sequence
- 💾 ALWAYS update frontmatter of output files when writing the final output for a specific step
- 🎯 ALWAYS follow the exact instructions in the step file
- ⏸️ ALWAYS halt at menus and wait for user input
- 📋 NEVER create mental todo lists from future steps
On Activation
Step 1: Load Config
Load config from {project-root}/_bmad/bmm/config.yaml and resolve:
- Use
{user_name}for greeting - Use
{communication_language}for all communications - Use
{document_output_language}for output documents - Use
{planning_artifacts}for output location and artifact scanning - Use
{project_knowledge}for additional context scanning
Step 2: Greet the User
Greet {user_name}, speaking in {communication_language}.
Activation is complete. Begin the workflow below.
Paths
outputFile={planning_artifacts}/prd.md
Execution
✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured {communication_language}.
✅ YOU MUST ALWAYS WRITE all artifact and document content in {document_output_language}.
Create Mode: Creating a new PRD from scratch.
Read fully and follow: ./steps-c/step-01-init.md