ralph

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

232|38|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/rohunj/claude-build-workflow --skill ralph-rohunj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/rohunj/claude-build-workflow/tree/main/skills/ralph
Command: npx skills add https://github.com/rohunj/claude-build-workflow --skill ralph-rohunj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converting PRDs into Ralph-compatible prd.json formats to enable autonomous execution by the Ralph agent.

Core Features & Use Cases

  • Converts a PRD (markdown or text) into a single prd.json with fields like project, branchName, description, and userStories.
  • Ensures each user story is sized for one Ralph iteration and validated by typecheck requirements, with clear acceptance criteria.

Quick Start

Provide a PRD (markdown or text) and this skill will generate a Ralph-ready prd.json.

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 to prd.json for autonomous agent processing?

Converting a PRD to prd.json requires transforming markdown or plain text into a structured schema with project, branchName, description, and userStories fields. This skill outputs a Ralph-ready prd.json formatted for autonomous execution.

What is the prd.json schema format for the Ralph autonomous agent system?

The prd.json schema includes project, branchName, description, and userStories fields. It requires kebab-case branch names and one user story per Ralph iteration, validated by typecheck requirements and clear acceptance criteria.

Can I use markdown format PRDs to generate a prd.json file?

Yes, markdown format PRDs are supported for prd.json generation. The skill accepts both markdown and plain text PRD inputs and converts them into a fresh, archivable prd.json state ready for Ralph processing.

How should user stories be structured in a prd.json for Ralph?

User stories in prd.json must be sized for one Ralph iteration each, with clear acceptance criteria and typecheck requirements. The conversion ensures one story per US to maintain a fresh, archivable state.

What are the limitations when converting PRDs to Ralph-ready prd.json?

The conversion requires strict adherence to Ralph rules: one story per US, kebab-case branchName, and typecheck validation. PRDs lacking clear acceptance criteria may not convert properly into the prd.json schema.