ralph

Convert PRD markdown and task files into executable JSON configurations.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/vitoropereira/claude-starter-kit --skill ralph-vitoropereira
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/vitoropereira/claude-starter-kit/tree/main/.claude/skills/workflow/ralph
Command: npx skills add https://github.com/vitoropereira/claude-starter-kit --skill ralph-vitoropereira

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the conversion of Product Requirement Documents (PRDs) and their associated tasks into a structured JSON format, enabling autonomous execution by the Ralph system.

Core Features & Use Cases

  • PRD to JSON Conversion: Parses PRD markdown files and task details to generate prd-XX.json.
  • Task Structuring: Organizes tasks with IDs, titles, acceptance criteria, and file modifications.
  • Use Case: When you have a new feature defined in a PRD and its tasks documented, use this Skill to prepare it for automated implementation by Ralph.

Quick Start

Use the ralph skill to convert the prd located at docs/prds/PRD-01-critical-fixes.md into ralph json format.

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 markdown file into a structured JSON format?

Converting PRD markdown into structured JSON requires parsing the document alongside associated task files to generate executable configurations. This Skill extracts task IDs, titles, and acceptance criteria to organize autonomous execution workflows.

What is the process for structuring tasks from a PRD for autonomous execution?

Structuring tasks for autonomous execution involves organizing parsed PRD details into specific IDs, titles, acceptance criteria, and file modifications. This ensures the generated JSON configuration adheres to the strict sizing and ordering conventions required for automated implementation.

Do I need specific acceptance criteria conventions to generate executable JSON from PRDs?

Yes, you need specific acceptance criteria conventions to generate executable JSON from PRDs. Adhering to required task sizing, ordering, and acceptance criteria rules is necessary for successful autonomous workflow generation.

Can I use directory-specified task details to create an automated workflow configuration?

Yes, you can use directory-specified task details to create an automated workflow configuration. The conversion process parses PRD markdown and task details from specified directories to generate the executable JSON file.

What are the limitations when converting Product Requirement Documents into executable JSON?

A key limitation when converting Product Requirement Documents into executable JSON is the strict dependency on specific task sizing, ordering, and acceptance criteria conventions. Failing to meet these structural requirements prevents successful autonomous workflow generation.