ralph

Converts Markdown PRDs into prd.json and resets progress for Ralph automation.

4|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/tech-with-seth/iridium --skill ralph-tech-with-seth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/tech-with-seth/iridium/tree/main/.github/skills/ralph
Command: npx skills add https://github.com/tech-with-seth/iridium --skill ralph-tech-with-seth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the handoff between product requirement documentation and Ralph-driven execution by converting Markdown PRDs into a standard prd.json format and setting up the execution context.

Core Features & Use Cases

  • PRD to JSON conversion: Read a Markdown PRD from tasks/prd-[feature].md and generate plans/prd.json in a Ralph-ready structure.
  • Handoff preparation: Archive any previous Ralph run and reset progress logs to ensure a clean iteration.
  • Execution readiness: Prepare branch names and environment instructions for Ralph to execute planned user stories.

Quick Start

Use the Ralph preparation script from the repository root to convert the latest PRD into plans/prd.json and reset progress.

  • Ensure a PRD exists at tasks/prd-[feature].md
  • Run: ./plans/ralph.sh 20

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 workflow automation?

To convert a Markdown PRD to JSON, place your file at tasks/prd-[feature].md and run the preparation script to generate a Ralph-ready plans/prd.json structure for automation.

What is a prd.json file used for in automated task execution?

A prd.json file standardizes product requirements into a structured format that automation workflows read to execute planned user stories without manual intervention.

Do I need a specific file path for my PRD to generate the JSON output?

Yes, your PRD Markdown file must be located at tasks/prd-[feature].md to successfully generate the plans/prd.json output and prepare the environment for automated execution.

How do I reset progress for a new automation run without losing previous data?

To reset progress for a new automation run, the conversion process archives previous iterations automatically, ensuring a clean environment while preserving past execution logs.

Can I run the PRD conversion directly from my repository root?

Yes, you can run the PRD conversion directly from the repository root by executing the ./plans/ralph.sh script to prepare branch names and execution instructions.