ralph

Convert product requirement documents into Ralph's prd.json user story format.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/raseniero/jodex_wiggum_coding_agent --skill ralph-raseniero
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/raseniero/jodex_wiggum_coding_agent/tree/main/skills/task
Command: npx skills add https://github.com/raseniero/jodex_wiggum_coding_agent --skill ralph-raseniero

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the conversion of Product Requirements Documents (PRDs) into the structured prd.json format required by the Ralph autonomous agent system, streamlining the process of defining features and user stories for development.

Core Features & Use Cases

  • PRD to JSON Conversion: Transforms markdown or text-based PRDs into Ralph's specific JSON schema.
  • User Story Structuring: Organizes feature requirements into discrete, actionable user stories with acceptance criteria.
  • Use Case: You have a detailed PRD for a new feature. Use this Skill to convert it into the prd.json format, ensuring all user stories are correctly defined, sized, and ordered for Ralph to execute.

Quick Start

Use the ralph skill to convert this PRD into prd.json format.

Frequently Asked Questions about ralph

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

FAQPage Schema
How do I convert a PRD into JSON format for autonomous agents?

Converting a PRD into structured JSON requires mapping project details and feature descriptions into discrete user stories. Each story needs a unique ID, title, technical specifications, acceptance criteria, and priority to ensure it is sized for single iteration completion and ordered by dependency.

What is the prd.json format used for in product management?

The prd.json format structures product requirement documents for the Ralph autonomous agent system. It organizes features into actionable user stories with detailed technical specifications, acceptance criteria, and priority levels so the agent can execute development tasks.

How do I structure user stories from a product requirement document?

Structuring user stories from a PRD involves breaking down feature descriptions into discrete objects with unique IDs, titles, technical specifications, acceptance criteria, and priority. Stories must be sized for single iteration completion and ordered by dependency.

Can I use markdown PRDs to generate structured user stories with acceptance criteria?

Yes, markdown or text-based PRDs can be transformed into a structured JSON schema containing user stories. The conversion process defines detailed story objects including technical specifications, acceptance criteria, and priority for autonomous execution.

What are the requirements for sizing user stories in agile development?

User stories in this context must be sized for single iteration completion. They are structured with specific IDs, titles, descriptions, technical specifications, acceptance criteria, and priority, and then ordered by dependency to facilitate autonomous development.

Does PRD to JSON conversion support dependency ordering for development tasks?

PRD to JSON conversion ensures stories are ordered by dependency. The structured output includes feature names, descriptions, and detailed user story objects with priority and technical specifications to guide the autonomous agent system.