prd

Generate a structured PRD with goals, user stories, and success metrics.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate clear, implementation-ready Product Requirements Documents from a feature prompt, aligning teams on goals, scope, and success criteria.

Core Features & Use Cases

  • Structured PRD sections: Introduction, Goals, User Stories, Functional Requirements, Non-Goals, Design Considerations, and Open Questions.
  • Clarifying questions: The skill guides users through 3-5 essential questions to resolve ambiguity before drafting the PRD.
  • Automated persistence: Saves the final PRD to tasks/prd-[feature-name].md for easy versioning and tracking.
  • Reuse of planning artifacts: References existing planning work when available to ensure consistency.

Quick Start

Provide a feature description (e.g., "Add streaming support") and let the skill ask clarifying questions and generate a PRD saved to tasks/prd-add-streaming.md.

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 from a feature idea?

To generate a PRD, provide a feature prompt and answer 3-5 clarifying questions to resolve ambiguity. The tool then drafts a structured document with goals, user stories, and acceptance criteria, saving it to tasks/prd-[feature-name].md.

What sections are included in a product requirements document for new features?

A product requirements document includes Introduction, Goals, User Stories, Functional Requirements, Non-Goals, Design Considerations, Open Questions, and Success Metrics. Each user story features explicit acceptance criteria and verifiable completion criteria.

How do I write user stories with acceptance criteria for project planning?

Writing user stories with acceptance criteria involves answering targeted questions about your feature prompt. The system structures your goals into actionable user stories, applying explicit acceptance criteria and verifiable completion metrics for each scenario.

Can I use this for planning any new feature or project?

Yes, you can use this for planning any new feature or project. It applies to general product management planning, referencing existing planning artifacts when available to ensure consistency across your project scope and requirements.

What is the best way to define non-goals and success metrics in a PRD?

The best way to define non-goals and success metrics is through guided clarification. By answering initial questions about your feature, the tool automatically formulates boundaries with non-goals and establishes verifiable success metrics.