checkpoint

Generates concise progress summaries for agent-session handoffs in .thoughts/iteration directories.

1|Updated Jan 24, 2023
One-click install
npx skills add https://github.com/KaiNakamura/dotfiles --skill checkpoint-kainakamura
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/KaiNakamura/dotfiles/tree/main/claude/skills/checkpoint
Command: npx skills add https://github.com/KaiNakamura/dotfiles --skill checkpoint-kainakamura

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lost context between agent sessions slows progress and reduces efficiency. This skill generates a concise progress summary to preserve critical context for the next session.

Core Features & Use Cases

  • Identify the current iteration by locating the highest iteration-NN/ directory inside .thoughts/.
  • Update or create the progress at .thoughts/iteration-NN/progress.md with sections for Completed Tasks, Current State, Key Decisions, and Context for Handoff.
  • Provide a ready-to-use handoff document that speeds up continuation and reduces rework across agent instances.

Quick Start

Create or update the progress summary at the path .thoughts/iteration-NN/progress.md to reflect the latest Completed Tasks, Current State, Key Decisions, and Handoff Context.

Frequently Asked Questions about checkpoint

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

FAQPage Schema
How do I preserve agent context between sessions for task handoff?

To generate a progress summary, the skill identifies the highest iteration-NN directory inside .thoughts/ and updates the progress.md file with sections for Completed Tasks, Current State, Key Decisions, and Context for Handoff.

What is the best way to track iterative task progress for agent workflows?

No external dependencies are required beyond standard file IO. The skill enforces that the summary is stored as a machine-readable document, requiring no additional libraries or frameworks to function in your environment.

How do I create a handoff document for an ongoing iteration?

This approach is designed for iterative agent workflows that use a .thoughts/ directory structure. If your project does not use this iteration-based directory pattern, you will need to establish it before generating progress summaries.

Why does my agent lose context when resuming an iterative workflow?

Unlike generic documentation, this approach creates a machine-readable handoff document structured specifically for agent sessions. It focuses on preserving actionable context like key decisions and current state rather than unstructured notes.