ralph-state-manager

To synchronize task and test lifecycles across markdown files, this Skill automates Start/Finish transitions, updating statuses consistently across 04-ralph-tasks.md, 05-test-plan.md, and the aggregate RALPH_STATE.md file to prevent duplication.

Maintaining state consistency during Step 5 handovers requires enforcing tri-way synchronization among source-of-truth files and an aggregate state file, ensuring all task and test lifecycle actions are accurately reflected for reliable auditing.

You can automatically update task statuses by triggering Start/Finish actions within the Ralph workflow context, which reads the authoritative source files and writes the synchronized lifecycle changes directly into RALPH_STATE.md.

Aggregate state management for file-based tracking works by reading authoritative sources like 05-test-plan.md for test outcomes and 04-ralph-tasks.md for task statuses, then writing only to the aggregate RALPH_STATE.md to enforce strict consistency.

No external dependencies are required to synchronize Ralph workflow state, as this Skill operates independently to read from authoritative markdown source files and write solely to the aggregate state file to enforce lifecycle consistency.

You should not use an automated state manager for task lifecycle transitions outside of the Ralph workflow context, as it specifically relies on reading 04-ralph-tasks.md and 05-test-plan.md to enforce strict tri-way file-based consistency.