checkpoint

Execute one phase of a multi-phase plan per session with structured handoff.

1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/s0lci700/OVERLAYS --skill checkpoint-s0lci700
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/s0lci700/OVERLAYS/tree/main/.claude/skills/checkpoint
Command: npx skills add https://github.com/s0lci700/OVERLAYS --skill checkpoint-s0lci700

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large multi-phase tasks often exceed rate limits, leaving work incomplete. Checkpoint enables executing one phase per session and providing a clear handoff for the next session.

Core Features & Use Cases

  • Execute a single phase of a plan per session, preventing overruns due to rate limits.
  • Provide a handoff summary for continuing work in the next session.
  • Use when tackling long-term projects that must be paused between phases.

Quick Start

Provide the phase number and plan description after calling /checkpoint, and I will execute that phase and stop.

Frequently Asked Questions about checkpoint

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

FAQPage Schema
How do I manage a multi-phase task workflow when hitting rate limits?▼

Breaking large objectives into consecutive sprint-like intervals allows you to execute one phase per session and output a structured handoff, ensuring no incomplete work is left when rate limits truncate the session.

How do I execute one phase of a plan and stop cleanly?▼

You execute one phase of a plan by providing the phase number and plan description, which enforces a strict phase boundary and outputs a structured handoff summary for the following session to resume work cleanly.

What is a structured handoff for continuing work in the next session?▼

A structured handoff for continuing work is the summary output generated after completing a single phase of a plan, allowing the next session to resume the multi-phase workflow seamlessly without losing context.

Can I use phase boundaries to prevent incomplete work from rate limits?▼

Yes, enforcing phase boundaries prevents incomplete work from rate limits by restricting execution to exactly one phase per session and requiring a structured handoff before stopping.

Do I need to provide a plan description to start a task phase?▼

Yes, you need to provide both the phase number and the plan description as input to execute that specific phase and generate the handoff summary for the next session.