ralph-wiggum

Iterative TDD development using a PRD is managed by creating a prd.json with tasks and maintaining a CONTEXT.md log. An external loop script spawns one task per iteration, records progress, and loops until all tasks are complete.

An external loop in TDD plan management is a script that orchestrates iterative development by spawning one task per iteration from a prd.json file. It records progress in CONTEXT.md and loops until all tasks are complete.

TDD iteration progress is tracked across tasks using a persistent CONTEXT.md log that records iteration progress. Combined with a prd.json containing tasks and passes tracking, it maintains a complete history of development progress.

Yes, Playwright and unit-test verification can be enforced in a TDD workflow as part of the task completion workflow. The external loop ensures verification discipline by requiring tests pass before moving to the next iteration.

Yes, a prd.json file with tasks is required to start iterative TDD planning. You also need a CONTEXT.md progress log and the ralph-external-loop script to orchestrate iterations and progressively complete all work.

The best way to run one task at a time in a TDD development plan is using an external loop script that spawns tasks sequentially. It processes a single task per iteration, records progress in CONTEXT.md, and loops until completion.