ralph-task-executor

Sequential task execution works by applying a strict R-Loop protocol—LOAD, IMPLEMENT, VERIFY, COMMIT, LOOP—to complete development tasks in physical file order. It enforces dependency checks, lint, tests, and build validation while maintaining synchronized state tracking.

Task state tracking uses statuses such as [ ], [~], [x], and [-] to manage lifecycle stages, automatically synchronizing with RALPH_STATE.md. It blocks progress, triggers rollback, and notifies users when prerequisites prevent moving forward.

The R-Loop protocol defines a task lifecycle sequence—LOAD, IMPLEMENT, VERIFY, COMMIT, LOOP—that completes tasks in physical file order. It integrates dependency checks, tests, linting, and build validation while requiring explicit commit messages referencing task IDs.

No, tasks must be completed in physical file order. The strict sequential execution protocol blocks progress and triggers rollback if a task is attempted out of order, ensuring dependency checks and build validation are always satisfied before committing.

Task execution blocks and triggers rollback when prerequisite checks, lint, tests, or build validation fail. This strict enforcement prevents broken or incomplete commits, halting the R-Loop lifecycle until dependencies are resolved and state is synchronized.