plan-to-ralph

Convert Superpowers implementation plans into Ralph PRD format files.

5|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/adelrioj/claude-skills --skill plan-to-ralph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-to-ralph
Source: https://github.com/adelrioj/claude-skills/tree/main/skills/plan-to-ralph
Command: npx skills add https://github.com/adelrioj/claude-skills --skill plan-to-ralph

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, jq, claude, codex, and includes scripts (resource) components.

What problem does it solve?

Converts a Superpowers implementation plan into Ralph's prd.json format, enabling autonomous execution by Ralph with a seeded cross-iteration context. The plan remains the single source of truth; do not re-interview the user or regenerate requirements.

Core Features & Use Cases

  • Map plan tasks to Ralph user stories and generate Ralph-compatible PRD files.
  • Validate and seed cross-iteration context into the output artifacts.
  • Produce outputs: tasks/prd.json, tasks/progress.txt, tasks/findings.md, and guide branch resolution and handoff messaging.
  • Support optional architecture/design context via a companion design doc and plan-only inputs.
  • Do NOT run Ralph during conversion; user reviews the generated PRD first.

Quick Start

Provide the path to the implementation plan you want to convert, then run the converter to generate Ralph-ready PRD files.

Frequently Asked Questions about plan-to-ralph

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

FAQPage Schema
How do I convert an implementation plan into a PRD for autonomous execution?

Converting an implementation plan into a PRD involves mapping plan tasks to user stories and generating prd.json, progress.txt, and findings.md files. This validates inputs and seeds cross-iteration context without regenerating requirements.

What is a Ralph-ready PRD and when do I need it?

A Ralph-ready PRD is a structured product requirements document in prd.json format that enables autonomous execution by Ralph. You need it when transitioning from an implementation plan to automated task execution.

Does plan-to-ralph conversion require git and jq installed?

Yes, plan-to-ralph conversion requires git, jq, claude, and codex as dependencies. These tools support branch resolution, JSON processing, and handoff messaging to generate the final Ralph-compatible PRD files.

Can I include a design doc when mapping plan tasks to user stories?

Yes, you can include an optional companion design doc to provide architecture and design context when mapping plan tasks to user stories. The converter supports both plan-only inputs and plan-with-design-doc workflows.

What's the best way to generate prd.json from an implementation plan?

The best way to generate prd.json is to provide the implementation plan path and run the converter, which maps tasks to user stories, validates inputs, and outputs prd.json along with progress.txt and findings.md.

Why does my PRD conversion not run Ralph automatically?

PRD conversion does not run Ralph automatically because the implementation plan remains the single source of truth. Users must review the generated PRD files first before activating Ralph for autonomous execution.