ralph

Convert markdown PRDs into Ralph-compatible prd.json files.

1.4k|162|Updated Sep 5, 2025
One-click install
npx skills add https://github.com/inkeep/agents --skill ralph-inkeep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/inkeep/agents/tree/main/.agents/skills/ralph
Command: npx skills add https://github.com/inkeep/agents --skill ralph-inkeep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts unstructured PRDs into Ralph's prd.json format to enable autonomous agent planning and execution.

Core Features & Use Cases

  • PRD to prd.json conversion: Transforms a product requirement document into a Ralph-compatible JSON structure for a new agent project.
  • Branch-ready outputs: Generates branchName like ralph/feature-name to align with Ralph workflows.
  • Use Case: Given a PRD for a new feature, generate a prd.json describing the project, its user stories, and acceptance criteria in Ralph's format.

Quick Start

Provide a sample PRD as input to convert it into a prd.json placed in the Ralph directory.

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 into a JSON format for autonomous agent execution?

Converting a markdown PRD into a JSON format translates goals, user stories, and acceptance criteria into a structured prd.json file with fields like project, branchName, description, and userStories for Ralph-compatible downstream execution.

What is the prd.json structure needed to start an autonomous agent project branch?

The prd.json structure requires specific fields including project, branchName (like ralph/feature-name), description, and userStories to validate compatibility for downstream Ralph tooling and autonomous execution.

How do I generate a Ralph-compatible JSON file from a product requirements document?

Generating a Ralph-compatible JSON file from a product requirements document involves parsing the markdown input and mapping the goals and acceptance criteria into the prd.json format placed directly in the Ralph directory.

Does the PRD to JSON conversion process validate compatibility for downstream Ralph tooling?

Yes, the PRD to JSON conversion validates the generated prd.json structure to ensure it is fully compatible with downstream Ralph tooling and autonomous agent workflows before creating the new project branch.

Can I transform unstructured product requirements into a branch-ready JSON file automatically?

Transforming unstructured product requirements into a branch-ready JSON file automatically creates a valid prd.json complete with a designated branchName like ralph/feature-name to align with autonomous agent workflows.

What limitations exist when converting unstructured PRDs into a Ralph-compatible JSON structure?

The main limitation is that the conversion applies strictly to markdown PRDs and requirements documents, translating only goals, user stories, and acceptance criteria into the Ralph-compatible JSON structure without supporting other input formats.