ralph

Convert PRDs from markdown or text into Ralph-compatible prd.json files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converting PRDs into Ralph-compatible prd.json is usually manual and error-prone. This skill automates that transformation, enabling seamless integration into Ralph autonomous workflows.

Core Features & Use Cases

  • PRD-to-prd.json conversion: transforms a PRD (markdown or text) into Ralph's structured JSON.
  • Branch/metadata generation: creates a descriptive branchName and project description suitable for version control.
  • Use Case: feed a PRD summary into the skill and generate a ready-to-run prd.json in your Ralph directory.

Quick Start

Use the ralph skill to convert a sample PRD like "New login flow" into prd.json in your Ralph directory.

Frequently Asked Questions about ralph

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

FAQPage Schema
How do I convert a markdown PRD to prd.json for autonomous agent execution?

To convert a markdown PRD to prd.json, the skill parses your plain text or markdown file and outputs a branch-ready JSON file conforming to Ralph's schema with fields for project, branchName, description, and userStories.

What is the prd.json schema required for Ralph workflows?

The prd.json schema required for Ralph workflows includes four main fields: project, branchName, description, and userStories. This structured format enables autonomous agents to process your requirements automatically.

Do I need to manually format user stories when converting a PRD to JSON?

You do not need to manually format user stories when converting a PRD to JSON. The skill automatically transforms your plain text or markdown PRD into the required userStories structure within the output prd.json file.

Can I use plain text PRDs to generate a branch-ready JSON file for version control?

You can use plain text PRDs to generate a branch-ready JSON file. The skill creates a descriptive branchName and project description suitable for version control directly from your text input.

Where does the generated prd.json file get saved during PRD conversion?

The generated prd.json file is saved directly in your Ralph directory during PRD conversion. This ensures the output is immediately ready for automated processing by the Ralph autonomous agent.

What are the limitations of automating PRD to JSON conversion for autonomous workflows?

A limitation of automating PRD to JSON conversion is that the skill relies entirely on the input PRD clarity to generate accurate userStories and metadata. Poorly structured markdown or text may result in incomplete JSON schema mapping.