From jeredblu-tools
Creates comprehensive PRDs via guided conversational discovery for planning software projects. Covers features, audience, platforms, tech stack, and outputs structured docs/PRD.md.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jeredblu-tools:prd-creatorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create comprehensive Product Requirements Documents (PRDs) through structured conversation and research.
Create comprehensive Product Requirements Documents (PRDs) through structured conversation and research.
This skill transforms product ideas into detailed, actionable specifications through guided discovery. It produces a single comprehensive PRD that serves as the source of truth for development.
Output: docs/PRD.md (single file, comprehensive enough for planning agents to break down)
In Claude Code:
docs/PRD.md in project rootdocs/ folder if it doesn't existIn Claude Desktop:
Begin every session by introducing yourself briefly as a PRD specialist. Explain that you'll ask a series of clarifying questions to deeply understand their idea before generating a PRD. Then ask them to describe what they want to build.
Objective: Understand what the user wants to build, their context, and constraints.
The 70/30 Rule: Spend 70% of the conversation discovering what the user wants. Spend 30% educating them about options, trade-offs, and technologies they may not have considered. Both halves are essential — discovery without education produces shallow PRDs, education without discovery produces generic ones.
Approach:
Adapt questioning based on signals:
Ask clarifying questions dynamically (see references/questioning-patterns.md for framework)
Mandatory discovery areas — all must be covered before PRD generation:
Minimum question guidance: Expect to ask 10-15 questions minimum before having enough context to generate a thorough PRD. Simple projects may land at 10; complex ones at 15+.
In Claude Code: Use AskUserQuestion tool to ask one question at a time. Keep questions concise.
Use web search when:
When technologies come up (or should come up based on the idea):
Objective: Validate technical choices, research unknowns, fill gaps.
When to research:
Tool priority:
references/tool-integration.md)See references/tool-integration.md for detailed tool usage patterns.
Before generating the PRD, review all 11 mandatory discovery areas:
This is a hard gate — do not skip it.
Objective: Create structured, comprehensive PRD.
Structure:
references/prd-template.mdOutput:
PRD.mdObjective: Iterate with user to finalize specifications.
Approach:
In Claude Code:
# Create docs folder if needed
mkdir -p docs
# Save PRD
# File: docs/PRD.md
In Claude Desktop:
1. Thorough, not rushed
2. Behavior-first, implementation-second
3. Comprehensive single output
4. Educational support (the 30% that matters)
references/prd-template.md - Complete PRD structure with all sectionsreferences/questioning-patterns.md - Dynamic discovery frameworkreferences/tool-integration.md - How to use MCP servers and web searchreferences/output-examples.md - Example PRDs for different project typesnpx claudepluginhub jeredblu/jeredblu-marketplace --plugin jeredblu-toolsGenerates Chinese PRD documents (full, brief, or one-page) via guided interviews, templates, validation, and AI-agent optimizations. Saves to docs/prd dirs.
Generates Product Requirements Documents (PRDs) with user stories, success metrics, scope, technical considerations, and risks for product features.
Guides interactive creation of Product Requirements Documents (PRDs) through structured questions across 15 sections like executive summary and problem statement. Saves as Markdown file.