ralph-loop

Automating BMAD story backlog execution requires iterating through open items in a BACKLOG.md file until completion or blockage. Ralph Loop drives this by selecting the next story, running it in an isolated subprocess, and updating statuses until all items are resolved or a circuit breaker triggers.

Subprocess orchestration for story-driven development forces each story to execute in a fresh Claude subprocess. This isolation keeps the main context clean while tracking attempts and updating story status during backlog iteration.

Yes, a BACKLOG.md file is required as the source for workflow automation. The automation reads this file to select the next story based on its current status, ensuring traceability and continued progress without manual intervention.

A circuit breaker in backlog management stops automated iteration when progress stalls. It tracks attempts and halts the workflow safely if stories cannot be resolved, preventing infinite loops and ensuring the process stops only when all items are done or blocked.

You should avoid automated subprocess orchestration when your backlog items require shared context between stories or lack a clear status tracking mechanism. The process relies on isolated execution and a structured BACKLOG.md to determine when to stop or continue.