prd

Generate a structured PRD with clarifying questions and save to tasks/prd-[feature-name].md.

Updated Jan 9, 2026

Search Tags:#prd #user-stories #acceptance-criteria #product-requirements #clarifying-questions

Ready to run

npx skills add https://github.com/vickaul-ai/ralph-claude --skill prd-vickaul-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/vickaul-ai/ralph-claude/tree/main/skills/prd
Command: npx skills add https://github.com/vickaul-ai/ralph-claude --skill prd-vickaul-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams generate clear, comprehensive Product Requirements Documents (PRDs) from feature ideas, ensuring alignment before development.

Core Features & Use Cases

Structured PRD sections: Introduction, Goals, User Stories, Functional Requirements, Non-Goals, and Open Questions.
Interactive clarifying questions to resolve ambiguities before PRD generation.
Auto-saves output to tasks/prd-[feature-name].md for seamless integration into project workflows.
Reusable templates to standardize PRD quality across products.

Quick Start

Use the prd skill to generate a PRD from your feature description and save it 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 create a product requirements document from a feature idea?▼

A PRD structures feature ideas into actionable requirements. This skill generates a comprehensive PRD with Introduction, Goals, User Stories, Functional Requirements, and Non-Goals sections from your feature description, then saves it as a standardized markdown file for team handoff.

What's included in a structured PRD template?▼

A structured PRD contains Introduction, Goals, User Stories with acceptance criteria, Functional Requirements, Non-Goals, and Open Questions sections. This skill auto-generates each section from your feature description and incorporates clarifying questions to resolve ambiguities before development starts.

How do clarifying questions help with PRD generation?▼

Clarifying questions identify and resolve ambiguities in your feature description before the PRD is finalized. This ensures the requirements are complete and unambiguous, reducing misalignment between product and development teams.

Can I use PRDs to standardize documentation across multiple products?▼

Yes. This skill applies reusable PRD templates with consistent sections and formatting, ensuring quality and alignment across all your products. Each output saves to a standardized filename for easy integration into project workflows.

When should I generate a PRD during the product development cycle?▼

Generate a PRD during feature planning, project kickoff, or whenever you need to clarify requirements before handoff to development. It's most valuable early in the cycle to prevent scope creep and misalignment.

Where does the PRD file get saved after generation?▼

The PRD is automatically saved to tasks/prd-[feature-name].md, using your feature name in the filename for easy tracking and integration into your project management workflow.