ralph

Convert Product Requirement Documents into structured JSON for autonomous execution.

1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/fabis94/fabis-ralph-loop --skill ralph-fabis94
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/fabis94/fabis-ralph-loop/tree/main/src/uac-templates/skills/ralph
Command: npx skills add https://github.com/fabis94/fabis-ralph-loop --skill ralph-fabis94

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the conversion of human-readable Product Requirement Documents (PRDs) into a structured JSON format that the Ralph autonomous agent can understand and execute.

Core Features & Use Cases

  • PRD to JSON Conversion: Transforms markdown PRDs into the .ralph/prd.json format.
  • Story Structuring: Organizes requirements into discrete, actionable user stories with clear acceptance criteria.
  • Dependency Management: Enforces best practices for story ordering and acceptance criteria to ensure successful autonomous execution.
  • Use Case: You've written a detailed PRD for a new feature. Use this Skill to prepare it for the Ralph autonomous coding loop, ensuring each user story is well-defined and actionable.

Quick Start

Use the ralph skill to convert the attached 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 structured JSON for autonomous agent execution?

To convert a PRD into structured JSON, this Skill transforms markdown Product Requirement Documents into the `.ralph/prd.json` format, defining discrete user stories with verifiable acceptance criteria for autonomous agent execution.

How does PRD to JSON conversion handle user story dependencies and ordering?

PRD to JSON conversion enforces best practices for story ordering and dependency management, ensuring user stories are small, ordered correctly, and include verifiable acceptance criteria like typechecking and UI verification.

What acceptance criteria are generated when structuring user stories from a PRD?

When structuring user stories from a PRD, the generated JSON includes verifiable acceptance criteria such as typechecking and UI verification to ensure each story is well-defined and actionable for autonomous execution.

Can I use a markdown PRD to prepare requirements for an autonomous coding loop?

Yes, you can use a markdown PRD to prepare requirements for an autonomous coding loop by converting it into structured JSON, ensuring each user story is properly ordered and includes actionable acceptance criteria.

What is the best way to structure product requirements into actionable user stories?

The best way to structure product requirements into actionable user stories is converting them into a structured JSON format, organizing requirements into small, correctly ordered stories with clear, verifiable acceptance criteria.