checkpoint

Update task tracking files with progress, decisions, and blockers.

1|Updated Jan 16, 2026

Search Tags:#workflow #task management #progress tracking #checkpoint #context preservation #session recovery

Ready to run

npx skills add https://github.com/coreindustries/core-ai-template --skill checkpoint-coreindustries

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/coreindustries/core-ai-template/tree/main/.claude/skills/checkpoint
Command: npx skills add https://github.com/coreindustries/core-ai-template --skill checkpoint-coreindustries

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that your work on long-running tasks is not lost due to context compression or session interruptions, allowing for seamless continuation.

Core Features & Use Cases

Task Progress Tracking: Updates task status, notes decisions, and logs progress in dedicated files.
Context Preservation: Maintains a detailed record of work done, making it easy to resume development.
Use Case: After completing a significant coding module, use /checkpoint to save your progress, document key decisions made during implementation, and outline the next steps before switching to another task or taking a break.

Quick Start

Run the checkpoint skill to update your current task progress.

Frequently Asked Questions about checkpoint

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

FAQPage Schema

How do I preserve context and save task progress before an AI session compression?▼

To preserve context before session compression, you can use a progress tracking mechanism to update task files with current status, decisions, and blockers. This ensures your development context is fully recoverable when you resume work later.

What is the best way to recover session context for long-running features after an interruption?▼

Recovering session context for long-running features relies on updating dedicated task tracking files with progress summaries and next session priorities. This records your work done and outlines next steps for seamless continuation after interruptions.

How do I automatically update task tracking files with my current progress and blockers?▼

You can automatically update task tracking files by running a progress tracking command that detects the active task file. It updates sections including tasks, progress summaries, next session priorities, and session logs to document key decisions.

Does progress tracking for long-running tasks work without external dependencies?▼

Yes, progress tracking for long-running tasks works without external dependencies. It operates by automatically detecting and updating local task files to maintain a detailed record of work done, ensuring context preservation without requiring additional packages.

Can I document key decisions and next steps for long-running features before switching tasks?▼

Yes, you can document key decisions and next steps for long-running features before switching tasks. By logging your progress in dedicated files, the system updates task status and outlines next session priorities to ensure seamless continuation.

When should I not use automated task tracking for context preservation?▼

You should avoid automated task tracking for context preservation if your workflow does not utilize local task files. The mechanism specifically detects and updates active task files to log progress, requiring a file-based structure to function properly.