dan:resume

To resume a paused Claude session, load the position and context from the STATE.md file to continue execution from the saved point. This restores the phase, plan, task, stage, and wave data to seamlessly resume your pipeline.

Session state management for multi-step pipelines involves saving execution position and accumulated context to a file when pausing mid-task. When resuming, the system rehydrates this state and selects the next skill to invoke without manual re-entry.

Yes, the session resume process verifies the WIP pause point in git history and checks for uncommitted changes. This git validation ensures a safe resume by preventing state drift before delegating control to the next skill.

To restore accumulated context and decisions after pausing a workflow, the system loads previously saved blockers, summaries, and decisions from the state file. It then updates the status and last activity to reflect the resumed work.

The best way to prevent state drift when resuming a paused pipeline is to use a state management file that records the exact phase, task, and stage. The system validates the git WIP pause point and reloads the context before continuing execution.

You need to use a state file for pausing and resuming Claude tasks when working with multi-step pipelines where pausing occurs mid-task. It allows the system to determine the next skill and resume point without losing accumulated context.