ralph

To automate autonomous code iterations from a PRD markdown file, you can convert it into a structured prd.json to drive an autonomous development loop. This orchestrates feature-branch workflows, enforces TDD, and generates PR bodies for streamlined reviews.

TDD workflow automation with PRDs works by parsing the markdown into user stories, acceptance criteria, and test guidance. It then orchestrates feature branches from main, enforces TDD, and logs iteration progress with detailed commit messages for traceability.

Yes, you need GitHub CLI (gh) and jq installed to automate feature-branch workflows from main. These dependencies enable the autonomous loop to create branches, generate PR bodies, and process the structured prd.json required for round-trip reviews.

Yes, you can use Claude to enforce TDD and generate PR bodies automatically. The autonomous development loop uses Claude to orchestrate feature branches from main, log iteration progress, and create detailed commit messages and PR bodies for round-trip reviews.

The best way to convert PRD markdown into user stories and acceptance criteria is by transforming it into a structured prd.json file. This enables an autonomous loop that uses the structured data to enforce TDD and orchestrate feature-branch workflows.

Autonomous code iterations may not track progress if the PRD markdown is not properly converted to a structured prd.json. The loop relies on this structured format to generate detailed commit messages and log iteration progress on feature branches from main.