state-sync

Workflow state synchronization automatically updates phase, requirements status, plan status, and delivery readiness fields in a central state file whenever task transitions or file touches occur.

Workflow state synchronization prevents stale data by enforcing explicit, testable validation on state fields during planning, implementation, and delivery. You need it when managing complex phase transitions and blockers.

Update the central workflow state file immediately after any gate outcome changes, new files are touched, or a blocker appears to maintain accurate phase and status tracking across the project.

Yes, state synchronization operates without external dependencies by reading and writing directly to the .claude/workflow-state.json file to enforce consistent state validation.

Tracking task blockers and phase transitions consistently requires applying explicit state fields like implementation.status and delivery.status to a central state file, preventing stale data during delivery.

Workflow state files contain stale phase data when state changes are not explicitly synchronized after file touches or gate results, requiring automatic updates to maintain consistency.