ralph

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

5|1|Updated Jun 7, 2020
One-click install
npx skills add https://github.com/mseok/dot --skill ralph-mseok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/mseok/dot/tree/main/ai/codex/skills/ralph
Command: npx skills add https://github.com/mseok/dot --skill ralph-mseok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRDs and product briefs are often informal and scattered; this skill converts them into Ralph's prd.json structure to enable automated planning and execution.

Core Features & Use Cases

  • Convert a Markdown PRD or plain text into a prd.json with fields like project, branchName, description, and userStories.
  • Generate consistent branch names (ralph/<feature-name>) and an actionable planning description.
  • Use cases include turning existing PRDs into Ralph-ready artifacts for autonomous agents and pipeline automation.

Quick Start

Convert a sample PRD into a Ralph-compatible prd.json to begin automated planning.

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 into a prd.json file for automation?

To convert a Markdown PRD into a prd.json file, you transform the plain text into a structured JSON schema mapping projects, branches, and user stories. This structures informal product briefs for automated pipeline execution.

What is the prd.json format used for autonomous agent execution?

The prd.json format structures product requirements into fields like project, branchName, description, and userStories for autonomous agents. It ensures automated execution by validating acceptance criteria and enforcing branch naming conventions.

Can I use plain text product briefs to generate user stories for automated planning?

Yes, you can use plain text product briefs to generate user stories for automated planning. The conversion process extracts requirements from the text and maps them into structured userStories within the prd.json schema.

How do I validate acceptance criteria when converting a PRD to JSON?

Validating acceptance criteria when converting a PRD to JSON involves mapping the requirements to the target schema and performing type checks. This ensures the generated userStories meet the structural rules required by the autonomous agent.

Does converting a PRD support branch naming conventions like ralph/<feature-name>?

Yes, converting a PRD supports branch naming conventions like ralph/<feature-name>. The transformation process generates consistent branch names within the prd.json file to enable actionable and automated project planning.