prd

Generate a structured PRD from a feature description with guided questions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating PRDs from feature ideas is often manual and error-prone; this skill automates the creation of a structured PRD to clarify scope, goals, success criteria, and deliverables.

Core Features & Use Cases

  • Automated PRD structure generation from a feature description, including Introduction, Goals, User Stories, Acceptance Criteria, Functional Requirements, and Non-Goals.
  • Guided clarifying questions (3-5) with multiple-choice options to resolve ambiguity before generation.
  • Output saved to tasks/prd-[feature-name].md for version control and traceability.
  • Optional sections for Design Considerations and Technical Considerations to assist engineering teams.

Quick Start

Provide a concise feature description and goals, and the tool will generate a complete PRD saved to tasks/prd-[feature-name].md.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I write a product requirements document from a feature idea?

To write a product requirements document from a feature idea, provide a concise feature description and the tool generates a structured PRD covering goals, user stories, requirements, and acceptance criteria. It saves the output as a markdown file for version control and traceability.

What should be included in a PRD for a new software feature?

A PRD for a new software feature should include Introduction, Goals, User Stories, Acceptance Criteria, Functional Requirements, and Non-Goals. Optional sections for Design and Technical Considerations can also be included to assist engineering teams with implementation planning.

How do I generate testable acceptance criteria for user stories?

To generate testable acceptance criteria for user stories, the tool applies a guided process that asks 3 to 5 clarifying multiple-choice questions to resolve ambiguity. This ensures the resulting acceptance criteria in the PRD are structured, clear, and testable.

Can I automatically create a markdown specification document for project planning?

Yes, you can automatically create a markdown specification document for project planning. The tool takes your feature description and outputs a complete PRD saved directly to a tasks directory as a markdown file, enabling version control and traceability.

Do I need any technical dependencies to generate a PRD?

No technical dependencies are required to generate a PRD. You only need to provide a concise feature description and goals, and the tool independently handles the structured generation of the product requirements document.