checkpoint-resume

Save pipeline progress to a JSON state file after each phase.

217|20|Updated Dec 31, 2025
One-click install
npx skills add https://github.com/yonatangross/orchestkit --skill checkpoint-resume-yonatangross
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkpoint-resume
Source: https://github.com/yonatangross/orchestkit/tree/main/plugins/ork/skills/checkpoint-resume
Command: npx skills add https://github.com/yonatangross/orchestkit --skill checkpoint-resume-yonatangross

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and rules (resource) components.

What problem does it solve?

This Skill ensures long, multi-phase tasks survive interruptions like rate limits or accidental session closures by saving progress and allowing easy resumption.

Core Features & Use Cases

  • Rate-Limit Resilience: Automatically saves progress to .claude/pipeline-state.json after each phase.
  • Resumable Workflows: If interrupted, the Skill prompts to resume from the last saved point or a chosen phase.
  • Use Case: Implementing a complex feature that involves creating GitHub issues, writing code, and then committing. If the process is interrupted, you can pick up exactly where you left off without losing work.

Quick Start

Resume an interrupted pipeline by invoking the checkpoint-resume skill.

Frequently Asked Questions about checkpoint-resume

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume a multi-phase pipeline after hitting a rate limit or session interruption?

To resume an interrupted pipeline, this Skill saves progress to a JSON state file after each phase, allowing you to restart the workflow from the last saved point or a chosen phase without losing completed work.

What is the best way to manage complex workflows that span multiple commits and file changes safely?

Managing complex workflows safely requires saving pipeline state after each phase, utilizing mini-commits and structured phase ordering rules to ensure file changes and commits are tracked and resumable upon interruption.

How do checkpoint state files work for resilient pipeline orchestration?

Checkpoint state files work by writing pipeline progress to a JSON file after every phase completes, recording the current phase ordering and status so the orchestration can gracefully handle interruptions and resume seamlessly.

Can I resume a long task from a specific phase instead of starting over?

Yes, you can resume a long task from a specific phase. When invoked after an interruption, the Skill prompts you to resume directly from the last saved checkpoint or select a chosen phase to restart the workflow.

Do I need to configure anything to enable workflow resumption for my automated tasks?

No special configuration is needed. The Skill utilizes initialization scripts to automatically set up the JSON state file and display status, enabling resumable workflows for your automated tasks out of the box.

What are the limitations of using JSON state files for pipeline checkpointing?

Using JSON state files for pipeline checkpointing limits state tracking to phase ordering and completion status, meaning complex nested workflow branching or highly parallel pipeline execution might not be fully captured without custom rules.