prd

Generate Markdown PRDs through a structured five-step question workflow.

11|2|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/davidkimai/ralph-zero --skill prd-davidkimai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/davidkimai/ralph-zero/tree/main/skills/prd
Command: npx skills add https://github.com/davidkimai/ralph-zero --skill prd-davidkimai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual, error-prone PRD creation slows feature delivery and leads to misaligned scope and acceptance criteria across stakeholders.

Core Features & Use Cases

  • Interactive Q&A workflow to elicit feature details (problem, goals, users, scope, constraints, success metrics)
  • Generates a complete PRD with sections: executive summary, problem statement, goals, user stories (with acceptance criteria), functional requirements, non-goals, technical approach
  • Outputs in Markdown and can be converted to prd.json with an external skill

Quick Start

Describe the feature you want to document, and the skill will generate a production-ready PRD.

Frequently Asked Questions about prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a PRD with user stories and acceptance criteria?

To generate a PRD with user stories and acceptance criteria, describe your feature to initiate a guided question-and-answer workflow that elicits problems, goals, and scope to output a structured Markdown document.

What sections are included in a generated product requirements document?

A generated product requirements document includes sections for an executive summary, problem statement, goals, user stories with acceptance criteria, functional requirements, non-goals, and a technical approach.

Can I convert the Markdown PRD output to prd.json?

Yes, you can convert the Markdown PRD output to prd.json format using an external skill, allowing integration of your generated product requirements into downstream development tracking systems.

What is the best way to document feature scope for cross-functional teams?

The best way to document feature scope for cross-functional teams is using a structured question-driven workflow to systematically align stakeholders on problems, goals, and functional requirements within a standardized PRD format.

Do I need prior product management experience to create requirements with this workflow?

No prior product management experience is required to create requirements, as the interactive question-driven workflow guides you step-by-step through defining problems, goals, users, scope, and success metrics.