productionos-pause

To pause a long-running pipeline and save its state, this skill creates a checkpoint at .productionos/CHECKPOINT.json that captures the active command, step, iteration, timestamp, grade, artifacts, and uncommitted_files for later resumption.

When suspending a multi-agent workflow, the checkpoint preserves command, step, iteration, timestamp, grade, artifacts, uncommitted_files, pending_batches, and context_notes by reading CONVERGENCE-LOG.md and CONVERGENCE-DATA.json without committing changes.

To resume an upgrade workflow from a saved checkpoint, you use the /productionos-resume command to reload the exact working state previously captured in the .productionos/CHECKPOINT.json file without losing context.

Pausing the orchestration pipeline does not commit your uncommitted files to git. It checks the git status and writes a checkpoint preserving the exact working state, leaving files uncommitted for later resumption.

Yes, you can use checkpointing for audit workflows across multi-agent orchestration. It applies to long-running upgrade and audit workflows, enabling suspension and later resumption without losing the active pipeline context.