ralph

Convert PRD documents into Ralph's prd.json format with structured fields.

632|201|Updated Jun 21, 2018
One-click install
npx skills add https://github.com/garyexplains/examples --skill ralph-garyexplains
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/garyexplains/examples/tree/main/ralph/skills/ralph
Command: npx skills add https://github.com/garyexplains/examples --skill ralph-garyexplains

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts a PRD (Product Requirements Document) into Ralph's prd.json format, enabling automated interpretation by the Ralph autonomous agent and reducing manual reformatting.

Core Features & Use Cases

  • PRD to prd.json conversion: Transforms titles, goals, scope, and user stories into the Ralph JSON schema.
  • Branch and project metadata: Generates a suitable project name, branchName, and overall description for Ralph workflows.
  • Structured output ready for validation: Produces a complete prd.json with fields like project, branchName, description, and userStories, ready for typechecking and testing.

Quick Start

Provide a PRD in markdown or text, then run the Ralph PRD Converter to generate the prd.json in your ralph directory and review the resulting branchName and userStories.

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 agent execution?

To convert a PRD to JSON for autonomous execution, you can use a transformation tool that translates titles, goals, scope, and user stories into a structured JSON schema with project, branchName, description, and userStories fields.

What is the required JSON structure for a Ralph prd.json file?

The required Ralph prd.json structure enforces specific fields including project, branchName, description, and userStories, while also embedding Typecheck and Tests requirements within the acceptance criteria for validation.

How do I generate branch names from a Product Requirements Document?

Generating branch names from a Product Requirements Document involves translating the document's project titles and goals into a structured JSON format that automatically produces a suitable branchName for your deployment workflow.

Can I use a markdown PRD to generate a JSON file for automated testing?

Yes, you can provide a PRD in markdown or text format to generate a complete JSON file that includes user stories with Typecheck and Tests requirements built directly into the acceptance criteria.

Does the PRD to JSON conversion process include acceptance criteria for validation?

Yes, the PRD to JSON conversion process enforces a structured output that includes Typecheck and Tests requirements as part of the acceptance criteria within each user story for automated validation.