checkpoint
Create, list, or recover mid-workflow checkpoints so interrupted work resumes from a known-good position
Best use case
checkpoint is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
It is a strong fit for teams already working in Codex.
Create, list, or recover mid-workflow checkpoints so interrupted work resumes from a known-good position
Teams using checkpoint should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/checkpoint/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How checkpoint Compares
| Feature / Agent | checkpoint | Standard Approach |
|---|---|---|
| Platform Support | Codex | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create, list, or recover mid-workflow checkpoints so interrupted work resumes from a known-good position
Which AI agents support this skill?
This skill is designed for Codex.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Top AI Agents for Productivity
See the top AI agent skills for productivity, workflow automation, operational systems, documentation, and everyday task execution.
SKILL.md Source
# Checkpoint You create, list, or recover lightweight mid-workflow checkpoints that allow a crashed or interrupted workflow to continue from a known-good position rather than restart from scratch. ## Triggers Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description): - "save my place" → create checkpoint at current position - "mark progress" → create checkpoint - "pick up where we left off" → recover from most recent checkpoint - "what checkpoints exist" → list checkpoints - "resume from checkpoint" → recover from specified or latest checkpoint ## Trigger Patterns Reference | Pattern | Example | Action | |---------|---------|--------| | Create (named) | "checkpoint this as iteration-3-complete" | Run `aiwg checkpoint create --name iteration-3-complete` | | Create (anonymous) | "create a checkpoint" | Run `aiwg checkpoint create` | | List | "show available checkpoints" | Run `aiwg checkpoint list` | | Recover (latest) | "recover from the last checkpoint" | Run `aiwg checkpoint recover` | | Recover (specific) | "recover checkpoint ckpt_7b2f1a" | Run `aiwg checkpoint recover ckpt_7b2f1a` | ## Behavior When triggered: 1. **Extract intent**: - Which subcommand: `create`, `list`, or `recover`? - Is a name or checkpoint ID provided? - For recover, should it use the most recent checkpoint or a specific one? 2. **Run the appropriate subcommand**: ```bash # Create — anonymous aiwg checkpoint create # Create — named aiwg checkpoint create --name <name> # List all checkpoints aiwg checkpoint list # Recover — most recent checkpoint aiwg checkpoint recover # Recover — specific checkpoint by ID or name aiwg checkpoint recover <id> ``` 3. **Checkpoints vs. snapshots**: Checkpoints are lightweight — they record the current workflow phase and step plus any in-progress artifact paths, not full artifact checksums. Use snapshots for complete point-in-time captures; use checkpoints for crash recovery during active workflows. | | Checkpoint | Snapshot | |---|---|---| | **Purpose** | Crash recovery | Reproducibility | | **Size** | Small (phase + step + artifact refs) | Full (versions + checksums) | | **Created by** | Manual or agent loop (auto) | Manual only | | **Use for** | Resume interrupted run | Replay from known state | 4. **Automatic creation**: Agent loops create checkpoints automatically between iterations. Manual `create` supplements this for critical workflow milestones. 5. **Storage**: Checkpoints are stored in `.aiwg/checkpoints/` as lightweight JSON files. 6. **Report the result** — on create, confirm the checkpoint ID and position; on recover, confirm which step the workflow will resume from. ## Examples ### Example 1: Create a named checkpoint **User**: "Create a checkpoint after iteration 3 completes" **Extraction**: Create subcommand, name `iteration-3-complete` **Action**: ```bash aiwg checkpoint create --name iteration-3-complete ``` **Response**: "Checkpoint `iteration-3-complete` created (ID: `ckpt_7b2f1a`). Recorded position: Construction phase, iteration 3, step 12/15. In-progress artifacts: `.aiwg/working/tests/integration-plan-draft.md`. Stored at `.aiwg/checkpoints/ckpt_7b2f1a.json`." ### Example 2: List checkpoints **User**: "What checkpoints do we have?" **Extraction**: List subcommand **Action**: ```bash aiwg checkpoint list ``` **Response**: ``` ID Name Date Phase / Step ckpt_3a8c12 (auto) 2026-03-28 10:04:51 Construction / iter 1, step 8 ckpt_9f20de (auto) 2026-03-29 14:17:33 Construction / iter 2, step 15 ckpt_7b2f1a iteration-3-complete 2026-03-30 09:55:02 Construction / iter 3, step 12 ``` ### Example 3: Recover from the latest checkpoint **User**: "The workflow crashed — recover from the last checkpoint" **Extraction**: Recover subcommand, use most recent **Action**: ```bash aiwg checkpoint recover ``` **Response**: "Recovering from most recent checkpoint `iteration-3-complete` (ckpt_7b2f1a). Resuming Construction phase, iteration 3, step 12/15. In-progress artifact `.aiwg/working/tests/integration-plan-draft.md` reloaded. Ready to continue." ### Example 4: Recover from a specific checkpoint **User**: "Recover from checkpoint ckpt_9f20de" **Extraction**: Recover subcommand, ID `ckpt_9f20de` **Action**: ```bash aiwg checkpoint recover ckpt_9f20de ``` **Response**: "Recovering from checkpoint `ckpt_9f20de` (auto, 2026-03-29 14:17:33). Resuming Construction phase, iteration 2, step 15/15. No in-progress artifacts. Ready to continue from this position." ## Clarification Prompts If the user's intent is ambiguous: - "Should I create a new checkpoint here, list existing checkpoints, or recover from one?" - "Which checkpoint would you like to recover from — the most recent, or a specific one? Run `aiwg checkpoint list` to see what's available." ## References - @$AIWG_ROOT/src/cli/handlers/subcommands.ts — Checkpoint command handler - @$AIWG_ROOT/docs/cli-reference.md — CLI reference - @$AIWG_ROOT/agentic/code/addons/aiwg-utils/skills/snapshot/SKILL.md — Full workflow snapshots (compare to checkpoints)
Related Skills
aiwg-orchestrate
Route structured artifact work to AIWG workflows via MCP with zero parent context cost
venv-manager
Create, manage, and validate Python virtual environments. Use for project isolation and dependency management.
pytest-runner
Execute Python tests with pytest, supporting fixtures, markers, coverage, and parallel execution. Use for Python test automation.
vitest-runner
Execute JavaScript/TypeScript tests with Vitest, supporting coverage, watch mode, and parallel execution. Use for JS/TS test automation.
eslint-checker
Run ESLint for JavaScript/TypeScript code quality and style enforcement. Use for static analysis and auto-fixing.
repo-analyzer
Analyze GitHub repositories for structure, documentation, dependencies, and contribution patterns. Use for codebase understanding and health assessment.
pr-reviewer
Review GitHub pull requests for code quality, security, and best practices. Use for automated PR feedback and approval workflows.
YouTube Acquisition
yt-dlp patterns for acquiring content from YouTube and video platforms
Quality Filtering
Accept/reject logic and quality scoring heuristics for media content
Provenance Tracking
W3C PROV-O patterns for tracking media derivation chains and production history
Metadata Tagging
opustags and ffmpeg patterns for applying metadata to audio and video files
Audio Extraction
ffmpeg patterns for extracting audio from video files and transcoding between formats