task-continue

To resume spec implementation after hitting context limits, load the latest checkpoint data and re-dispatch the next batch through the three-phase pipeline. This prevents starting over by validating the git state and continuing exactly where the previous session paused.

Checkpoint-driven resumption is a workflow mechanism that loads the latest state and spec data to continue work without re-creating context. It verifies the correct git branch and commit before resuming to prevent drift, enabling teams to pick up where a previous run paused.

To continue a three-phase pipeline from the last checkpoint, re-dispatch the next batch through testers, implementers, and reviewers. The system writes updated checkpoint and task statuses after batch completion to ensure traceability for the spec.

Yes, branch and state validation prevents git drift when resuming tasks. It verifies the correct git branch and commit before re-launching the pipeline, ensuring the working state matches the checkpoint data and avoiding conflicting changes.

The best way to handle session breaks during task dispatch is to invoke a continuation command with the target spec name. This loads checkpoint data, validates the git state, and re-launches the pipeline to process the next batch without losing progress.

Your automated workflow may not be picking up from the last checkpoint due to a git state validation failure. The system verifies the correct git branch and commit before resuming, so any drift or incorrect branch state will halt the re-launch of the three-phase pipeline.