ralph

Converts Markdown or plain-text PRDs into validated prd.json files for the Ralph agent system.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/dennywu2966/denny-all-in-one --skill ralph-dennywu2966
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/dennywu2966/denny-all-in-one/tree/main/home/.claude/skills/ralph
Command: npx skills add https://github.com/dennywu2966/denny-all-in-one --skill ralph-dennywu2966

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRDs are often written in Markdown or plain text but lack a standardized, Ralph-ready representation. The Ralph PRD Converter ensures a consistent prd.json output that can be consumed by the Ralph pipeline, enabling automated planning and execution.

Core Features & Use Cases

  • PRD parsing: Accepts Markdown or plain-text PRDs and extracts structured metadata.
  • PRD-to-JSON transformation: Produces prd.json with fields: project, branchName, description, userStories, and optional archiving metadata.
  • Validation and guidance: Enforces the required fields, supports breaking down PRDs into US- stories following dependencies, and prepares outputs suitable for versioning and automation.

Quick Start

Provide a PRD document and run the Ralph converter to generate prd.json in the Ralph project 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 JSON for automated workflows?

Converting a Markdown PRD to JSON involves parsing plain-text or Markdown documents to extract structured metadata like project, branchName, description, and userStories. This transformation produces a validated prd.json file suitable for versioning and autonomous agent execution.

What fields are required in a prd.json file for the Ralph autonomous agent?

A prd.json file requires project, branchName, description, and userStories fields to be consumed by the Ralph autonomous agent system. Optional archiving metadata can also be included to support versioning and workflow automation.

How to generate a kebab-case branch name from a PRD document?

Generating a kebab-case branchName from a PRD document requires parsing the Markdown or plain-text input to derive a standardized branch identifier. This ensures the resulting prd.json output aligns with automated versioning and pipeline execution requirements.

Can I parse plain-text PRDs and break them down into user stories?

Yes, parsing plain-text PRDs allows you to extract structured metadata and break down requirements into US- stories following dependencies. The conversion process enforces required fields and provides clear error handling when inputs are malformed.

What happens when malformed PRD inputs are processed for JSON transformation?

When malformed PRD inputs are processed for JSON transformation, the converter provides clear error handling and validation guidance. It enforces required fields like project, branchName, description, and userStories to ensure the output is valid for the Ralph pipeline.

Does the Ralph PRD converter support dependency tracking for user stories?

Yes, the Ralph PRD converter supports breaking down PRDs into US- stories following dependencies. It parses Markdown or plain-text PRDs and outputs a validated prd.json that includes structured userStories for autonomous planning and execution.