ralph-tui-create-json

Convert PRDs into a flat prd.json structure for ralph-tui execution.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/strataga/claude-skill-inception --skill ralph-tui-create-json
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph-tui-create-json
Source: https://github.com/strataga/claude-skill-inception/tree/main/ralph-tui-create-json
Command: npx skills add https://github.com/strataga/claude-skill-inception --skill ralph-tui-create-json

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts PRDs into a prd.json structure suitable for autonomous execution by ralph-tui, enabling seamless handoff from planning to automation.

Core Features & Use Cases

  • PRD to JSON conversion: Extracts user stories, acceptance criteria, and dependencies from a PRD and outputs a flat, ralph-tui-ready prd.json.
  • Automation-friendly output: Produces a prd.json that can be consumed by the ralph-tui engine to execute tasks in sequence.
  • Use Case: Imagine you have a PRD with multiple user stories and acceptance criteria; this skill generates a compliant prd.json for autonomous execution.

Quick Start

Use this skill to convert a PRD into a prd.json file, then run ralph-tui against the generated file.

Frequently Asked Questions about ralph-tui-create-json

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

FAQPage Schema
How do I convert a PRD into JSON for autonomous task execution?

To convert a PRD into JSON, this Skill extracts user stories, acceptance criteria, and dependencies to output a flat prd.json structure ready for autonomous execution. It ensures proper formatting by mapping root fields like name, branchName, and description.

What is the required JSON structure for ralph-tui task generation?

The ralph-tui task generation requires a flat prd.json structure containing root fields name, branchName, description, and a userStories array. Each story must include properly formatted acceptance criteria and dependencies.

Does this PRD to JSON conversion work with user stories that have dependencies?

Yes, this PRD to JSON conversion specifically processes user stories containing dependencies. It extracts dependency information from the PRD and formats it into the prd.json structure so ralph-tui can execute tasks in the correct sequence.

Can I use this to generate a prd.json from PRDs with multiple user stories?

Yes, you can use this to generate a prd.json from PRDs containing multiple user stories. It applies to PRDs with multiple stories, extracting acceptance criteria and dependencies to produce a compliant JSON object for ralph-tui processing.

What's the best way to automate task planning from a PRD document?

The best way to automate task planning from a PRD is converting it into a flat prd.json file. This enables seamless handoff from planning to automation by allowing the ralph-tui engine to consume the JSON and execute tasks autonomously.

Why does my prd.json need specific root fields for ralph-tui?

Your prd.json needs specific root fields like name, branchName, description, and a userStories array because ralph-tui requires this structured format to properly parse and autonomously execute the generated tasks in sequence.