prd

Generate executable PRDs with structured stories and acceptance criteria.

6|1|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/Ven0m0/claude-config --skill prd-ven0m0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/Ven0m0/claude-config/tree/main/claude/skills/prd
Command: npx skills add https://github.com/Ven0m0/claude-config --skill prd-ven0m0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms raw ideas or descriptions into structured, executable Product Requirements Documents (PRDs) with actionable stories for autonomous development, streamlining the product planning and feature definition process.

Core Features & Use Cases

  • Idea to Executable Spec: Converts plain text ideas or markdown files into .ralph/prd.json format.
  • Story Generation: Splits features into manageable, ~10-15 minute development stories.
  • Validation & Refinement: Ensures stories are testable, secure, and scalable before finalization.
  • Use Case: You have a new feature idea for your AI agent, Ralph. You input the idea, and this Skill generates a detailed PRD with user stories, acceptance criteria, and test steps, ready for Ralph to begin development.

Quick Start

Use the prd skill to generate a PRD for Ralph from the idea file 'docs/ideas/new-feature.md'.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I generate an executable PRD from a plain text idea?

To generate an executable PRD from a plain text idea, input your description or idea file to create a `.ralph/prd.json` containing structured stories with acceptance criteria and test steps.

What is the best way to structure user stories for autonomous development agents?

Structuring user stories for autonomous development agents involves splitting features into manageable, 10-15 minute development stories with defined testability, dependencies, and security validations.

Can I use a markdown file as input for product requirements generation?

Yes, you can use a markdown file as input for product requirements generation by referencing your idea file path, which the system reads to produce the structured PRD output.

How are generated user stories validated before finalizing the PRD?

Generated user stories are validated against testability, dependencies, security, and scale requirements, followed by an iterative refinement process through user confirmation before finalization.

Does the PRD output format support direct execution by development agents?

Yes, the PRD output format supports direct execution by generating a `.ralph/prd.json` file specifically designed as an executable spec for Ralph and autonomous development agents.

What limitations exist when refining product requirements iteratively?

When refining product requirements iteratively, the main limitation is that finalization requires explicit user confirmation after validating stories against testability, security, and scale requirements.