ralph

To convert a markdown PRD to a structured JSON format, this Skill parses your existing text-based requirements and generates a Ralph-compatible prd.json file. The output includes structured project metadata, a standardized branchName, and formatted userStories.

Splitting a product requirements document into single-iteration user stories is handled by generating structured user stories (US-001, US-002) within the prd.json. It enforces a one-story-per-iteration execution model and provides guidance on PRD-to-iteration splitting.

Yes, you can use a plain text PRD with automated agents. This Skill accepts both Markdown and text PRDs, automatically structuring the content into a prd.json file with project metadata and user stories ready for Ralph agents.

Converting a PRD to prd.json does include a standardized branchName and test verification guidelines. The generated JSON structure contains project, branchName, description, and userStories fields, alongside typecheck and test verification guidance.

Automated agent execution requires a specific PRD JSON structure to reliably parse and execute product requirements. This format ensures agents receive structured userStories, clear project metadata, and a standardized branchName for consistent automated processing.

You need to generate a prd.json file from your product requirements when you want to enable autonomous Ralph agents to execute your project. It transforms static Markdown or text PRDs into an automated, structured execution format.