ralph-json-create-issues

You can convert a PRD markdown file into JSON by providing its file path. The tool parses plan-mode outputs from directories like .claude/plans or prds/ and generates a structured prd.json file for automated workflow execution.

Yes, markdown plan files in .claude/plans are fully supported. The tool scans this directory alongside plans/ and prds/ to detect and resolve dependsOn relationships across referenced PRDs for accurate dependency handling.

The best way to split a large PRD into single-iteration user stories is to ensure each story includes explicit acceptance criteria. The tool automatically right-sizes stories to fit within a single automation iteration and outputs them to a feature-specific JSON file.

Yes, the generated prd.json requires explicit acceptance criteria for each story. Correct dependencies and acceptance criteria are mandatory to ensure the output is compatible with the ralph-json-start-loop automation workflow.

To resolve dependsOn relationships when converting multiple PRD files, the tool automatically detects referenced PRDs across the prds/, plans/, and .claude/plans/ directories and populates the dependency fields in the final JSON output.

Your PRD to JSON conversion outputs to prds/[feature-name].json to ensure the generated stories are correctly organized and ready for the automation loop. This standardized output path is required for the workflow to locate and execute the planned stories.