ralph

Convert Markdown or plain text PRDs into Ralph's prd.json format.

6|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/fagnerjs/ralphi --skill ralph-fagnerjs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/fagnerjs/ralphi/tree/main/skills/ralph
Command: npx skills add https://github.com/fagnerjs/ralphi --skill ralph-fagnerjs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies converting existing PRDs written in Markdown or plain text into Ralph's standardized JSON format, facilitating autonomous execution workflows.

Core Features & Use Cases

  • PRD Conversion: Parses a given PRD and generates the required prd.json structure with project info, branch naming, description, and user stories.
  • Story Breakdown: Assists in splitting large features into smaller, manageable user stories suitable for Ralph iterations.
  • Automation: Automates the creation of branch names and prioritization based on dependencies and dependencies order.

Quick Start

Use the Ralph JSON converter to turn your project PRD into a Ralph-compatible prd.json for automated deployment and testing.

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 automated project planning?

Story breakdown is necessary when large features need to be split into smaller, manageable user stories suitable for Ralph iterations, enabling structured task management and ensuring compliance with Ralph's story structuring and splitting rules.

Can I use plain text PRDs to generate branch names and prioritization automatically?

Yes, you can use plain text PRDs to automate the creation of branch names and prioritization based on dependencies and their execution order, streamlining the deployment-ready JSON generation process.

Does this PRD converter require any specific dependencies to structure user stories?

No specific dependencies are required to structure user stories, as the Skill independently parses the provided PRD content and applies Ralph's story structuring rules to output the required JSON format.

What is the best way to structure dependencies in a deployment-ready prd.json file?

The best way to structure dependencies in a prd.json file is by utilizing the Skill's automated prioritization feature, which orders dependencies based on the parsed PRD requirements to ensure compliant autonomous execution.