checkpointing-patterns

Persist workflow progress to docs/{WORKFLOW}-PROGRESS.md and resume from the last completed phase.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill checkpointing-patterns
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: checkpointing-patterns
Source: https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit/tree/main/skills/checkpointing-patterns
Command: npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill checkpointing-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Long-running workflows often lose progress due to interruptions; this skill provides a robust checkpointing system to persist state and enable seamless resume across phases.

Core Features & Use Cases

  • Per‑phase progress tracking through docs/{WORKFLOW}-PROGRESS.md for workflows like /new-task, /legacy-project, and /new-project.
  • Enforced exit gates for each phase to ensure completion before moving forward.
  • Lifecycle templates and automated history logging to support restart, auditing, and recovery.

Quick Start

Start a workflow by creating the appropriate docs/{WORKFLOW}-PROGRESS.md and use it to drive phase progression with automatic updates.

Frequently Asked Questions about checkpointing-patterns

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

FAQPage Schema
How do I persist progress in long-running workflows and resume after an interruption?▼

To persist progress in long-running workflows, you can use a checkpointing system that saves phase state to a dedicated progress file, allowing the workflow to restart seamlessly from the last completed phase. This prevents data loss during interruptions.

What is the best way to track phase state in a multi-stage development project?▼

The best way to track phase state is by using a standardized lifecycle with start, save, update, resume, and finalize steps. This enforces per-phase exit gates to ensure each stage is fully completed before moving forward.

How does automated progress history logging work for workflow recovery?▼

Automated progress history logging works by continuously updating a template-driven progress file with phase state data. This creates an auditable history that supports workflow recovery, auditing, and restart from the last saved checkpoint.

Do I need a specific file format to manage workflow checkpointing?▼

Yes, this workflow checkpointing approach uses template-driven Markdown files, specifically formatted as docs/{WORKFLOW}-PROGRESS.md, to persist progress and drive phase progression automatically across your project phases.

Can I apply checkpointing and resume patterns to existing legacy projects?▼

Yes, you can apply checkpointing and resume patterns to existing legacy projects. The system supports workflows like /legacy-project and /new-task, enabling you to integrate state management and phase tracking into ongoing work.