ralph-planner

Automated lifecycle management is orchestrated by coordinating Planning, Implementation, and Testing phases across multiple rounds. It uses a defined template and a state file to enforce strict sequencing and guardrails for phase transitions, ensuring consistent progress tracking.

A state machine approach for task planning enforces strict sequencing by reading and updating a RALPH_STATE.md state file. This file reflects the current phase, tasks, and delivery status, ensuring alignment across stakeholders and preventing out-of-order phase transitions.

To start the workflow, you initialize the planning phase and begin Round 1, Step 1. This triggers the lifecycle management process, applying the template-driven state management defined in your assets to execute the first iteration.

Yes, a defined template in assets and a state file are required to coordinate lifecycle phases. These components provide the centralized, automated governance layer necessary to ensure repeatable, auditable planning templates and enforce strict sequencing across iterations.

Yes, ralph-planner tracks delivery status across multiple iterations by reading and updating a RALPH_STATE.md state file. It orchestrates three rounds of Planning, Implementation, and Testing phases, ensuring alignment and consistent progress tracking throughout the lifecycle.

Template-driven lifecycle orchestration is limited to workflows where teams iteratively refine requirements, execute tasks, and validate outcomes. It requires strict adherence to the state machine for phase transitions, which may not suit projects needing non-sequential or ad-hoc task execution.