ralph-convert

Convert PRD markdown into validated Ralph Zero prd.json format.

11|2|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/davidkimai/ralph-zero --skill ralph-convert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph-convert
Source: https://github.com/davidkimai/ralph-zero/tree/main/skills/ralph-convert
Command: npx skills add https://github.com/davidkimai/ralph-zero --skill ralph-convert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts markdown Product Requirements Documents into the structured prd.json format required by Ralph Zero, with comprehensive validation and story optimization.

Core Features & Use Cases

  • Read and parse PRD markdown to extract metadata, requirements, and user stories.
  • Generate a validated prd.json suitable for autonomous development loops.
  • Apply story sizing and validation rules to ensure tasks are appropriately scoped.

Quick Start

Provide the PRD markdown file path or content to convert into a validated prd.json.

Frequently Asked Questions about ralph-convert

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

FAQPage Schema
How do I convert a markdown PRD to JSON format?

Converting a markdown PRD to JSON involves parsing the markdown content to extract metadata, requirements, and user stories, then structuring them into a validated prd.json format for autonomous development loops.

What is prd.json validation for user stories?

Prd.json validation for user stories enforces story sizing rules, aligns acceptance criteria, and verifies correct dependency ordering to ensure tasks are appropriately scoped before entering autonomous development loops.

Can I use markdown PRD files for story splitting in autonomous development?

Yes, you can use markdown PRD files for autonomous development by converting them into a structured prd.json format, which applies story sizing, acceptance criteria alignment, and dependency ordering to generate validated user stories.

What's the best way to structure acceptance criteria and dependencies in a prd.json file?

The best way to structure acceptance criteria and dependencies in a prd.json file is to use a markdown-to-JSON converter that enforces acceptance criteria alignment and validates correct dependency ordering during the extraction process.

Why does my markdown PRD fail story sizing validation?

Markdown PRD story sizing validation fails when the extracted user stories are not appropriately scoped, lack aligned acceptance criteria, or have incorrect dependency ordering within the generated prd.json structure.