ralph

Convert PRDs into structured prd.json files for Ralph.

13|1|Updated Feb 28, 2026

Search Tags:#automation #json #conversion #prd #product-requirements #ralph

Ready to run

npx skills add https://github.com/KSDaemon/ralphy --skill ralph-ksdaemon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/KSDaemon/ralphy/tree/main/skills/ralph
Command: npx skills add https://github.com/KSDaemon/ralphy --skill ralph-ksdaemon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual conversion of product requirement documents (PRDs) into a machine‑readable format is time‑consuming and error‑prone. This Skill automates the transformation of PRDs into the prd.json schema required by the Ralph autonomous agent, ensuring consistency and readiness for single‑iteration development.

Core Features & Use Cases

Automatic PRD discovery: Reads the newest PRD from the .ralph/tasks/ directory.
Structured JSON output: Generates prd.json with project metadata, branch naming, ordered user stories, and verifiable acceptance criteria.
Story sizing & ordering: Enforces single‑iteration story size limits and dependency‑first ordering.
Branch naming conventions: Applies feat/, fix/, hotfix/, or chore/ prefixes based on PRD content.
Archiving: Safely archives previous prd.json and progress files when switching features.
Checklist validation: Performs pre‑save checks for completeness, verifiability, and correct ordering.

Quick Start

Say “convert this prd to ralph format” to generate a prd.json file for the current project.

Frequently Asked Questions about ralph

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

FAQPage Schema

How do I convert a product requirement document into a structured JSON format?▼

To convert a PRD into structured JSON, place the document in the .ralph/tasks directory and trigger the conversion. The system reads the newest PRD and outputs a prd.json file containing project metadata, branch naming, ordered user stories, and verifiable acceptance criteria.

What is the best way to automate PRD parsing for autonomous agent development?▼

Automating PRD parsing requires extracting project descriptions and user stories into a machine-readable prd.json schema. This ensures single-iteration development readiness by enforcing story size limits, dependency-first ordering, and verifiable acceptance criteria for autonomous agents.

How do I generate branch names from PRD content automatically?▼

Generating branch names from PRD content involves analyzing the document to apply standard prefixes like feat/, fix/, hotfix/, or chore/ based on the change type. This convention is embedded directly into the generated prd.json file for immediate repository integration.

Does PRD to JSON conversion support archiving previous task files?▼

PRD to JSON conversion supports archiving by safely moving previous prd.json and progress files when switching features. This ensures historical task data is preserved without manual intervention before generating the new structured JSON output.

How are user stories sized and ordered for single-iteration development?▼

User stories are sized and ordered for single-iteration development by enforcing strict size limits and applying dependency-first ordering. The conversion process performs checklist validation to ensure completeness, verifiability, and correct sequencing before saving the prd.json file.

Can I validate acceptance criteria before saving the prd.json file?▼

You can validate acceptance criteria before saving through built-in pre-save checks. The conversion process performs checklist validation to ensure each user story includes verifiable acceptance criteria, confirming completeness and correct ordering prior to generating the final JSON output.