ralph

Convert Markdown or text PRDs into Ralph-compatible prd.json structures.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert existing PRDs into Ralph-compatible prd.json format to enable automated orchestration by the Ralph agent.

Core Features & Use Cases

  • PRD to prd.json conversion for Ralph autonomous execution
  • Generates branchName, project, and structured userStories from a PRD
  • Handles typical PRD sections (title, goals, acceptance criteria) for consistent downstream processing

Quick Start

Provide a PRD or markdown text and convert it to 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 JSON for autonomous execution?

To convert a PRD to JSON, provide your markdown or text document to generate a structured prd.json containing branchName, project, and userStories with verifiable acceptance criteria.

What is a Ralph-compatible prd.json format?

A Ralph-compatible prd.json is a structured JSON file containing branchName, project, description, and userStories with verifiable acceptance criteria, where Typecheck passes is a mandatory criterion.

Can I use markdown text to generate userStories for automated PRD processing?

Yes, you can use markdown text to generate structured userStories. The conversion extracts goals and acceptance criteria from typical PRD sections to create consistent downstream processing outputs.

Does PRD to JSON conversion require verifiable acceptance criteria?

Yes, PRD to JSON conversion requires verifiable acceptance criteria for each user story, and Typecheck passes is a mandatory criterion to satisfy the conversion rules for autonomous execution.

What's the best way to structure PRDs for autonomous agent execution?

The best way to structure PRDs for autonomous execution is to include clear titles, goals, and acceptance criteria sections, which are then parsed into a JSON format with branchName and userStories.