checkpoint
Original:🇺🇸 English
Translated
[Tooling & Meta] Save memory checkpoint to preserve analysis context
2installs
Sourceduc01226/easyplatform
Added on
NPX Install
npx skill4agent add duc01226/easyplatform checkpointTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →Save Memory Checkpoint
Save current analysis, findings, and progress to an external memory file to prevent context loss during long-running tasks.
Summary
Goal: Persist current task context, findings, and progress to a checkpoint file for recovery after context compaction.
| Step | Action | Key Notes |
|---|---|---|
| 1 | Determine location | Filename: |
| 2 | Gather context | Task, findings, files analyzed/modified, progress, decisions |
| 3 | Write checkpoint file | Structured markdown with recovery instructions |
| 4 | Update todo list | Mark checkpoint creation complete |
Key Principles:
- Save checkpoints every 30-60 minutes during complex tasks
- Include file paths, line numbers, and exact findings -- be specific
- Always include recovery instructions for easy task resumption
Usage
Use this command when:
- Working on complex multi-step tasks (investigation, planning, implementation)
- Before expected context compaction
- At key milestones during feature development
- After completing significant analysis phases
Checkpoint File Location
Files are saved to:
plans/reports/checkpoint-{timestamp}-{slug}.mdInstructions
Create a checkpoint file with the following structure:
Step 1: Determine Checkpoint Location
bash
# Get current date for filename
date +%y%m%d-%H%MStep 2: Gather Context
Collect and document:
- Current Task - What are you working on?
- Key Findings - What have you discovered?
- Files Analyzed - Which files have been read/modified?
- Progress Summary - What's completed vs remaining?
- Important Context - Critical information to preserve
- Next Steps - What should be done next?
- Open Questions - Unresolved issues
Step 3: Write Checkpoint File
Create a markdown file at with:
plans/reports/checkpoint-YYMMDD-HHMM-{task-slug}.mdmarkdown
# Memory Checkpoint: [Task Description]
> Checkpoint created to preserve analysis context during [task type].
## Session Info
- **Created:** [timestamp]
- **Task:** [description]
- **Branch:** [git branch]
- **Phase:** [current phase]
## Current Task Summary
[Brief description of what you're working on]
## Key Findings
### Analysis Results
- [Finding 1]
- [Finding 2]
- [Finding N]
### Patterns Discovered
- [Pattern 1]
- [Pattern 2]
### Dependencies Identified
- [Dependency 1]
- [Dependency 2]
## Files Context
### Analyzed Files
| File | Purpose | Relevance |
| --------------- | --------- | --------------- |
| path/to/file.cs | [purpose] | High/Medium/Low |
### Modified Files
- `path/to/modified.ts` - [change description]
### Pending Files
- `path/to/pending.cs` - [why pending]
## Progress Summary
### Completed
- [x] [Completed item 1]
- [x] [Completed item 2]
### In Progress
- [ ] [Current item]
### Remaining
- [ ] [Remaining item 1]
- [ ] [Remaining item 2]
## Important Context
### Critical Information
[Information that must not be lost]
### Assumptions Made
- [Assumption 1]
- [Assumption 2]
### Decisions Made
- [Decision 1] - [rationale]
- [Decision 2] - [rationale]
## Next Steps
1. [Immediate next action]
2. [Following action]
3. [Subsequent action]
## Open Questions
- [ ] [Question 1]
- [ ] [Question 2]
## Recovery Instructions
To resume this task after context reset:
1. Read this checkpoint file
2. Review [specific files] for context
3. Continue from [specific point]
---
_Checkpoint saved by Claude Code at [timestamp]_Step 4: Update Todo List
Update your todo list to reflect checkpoint was created:
- [x] Create memory checkpoint at [timestamp]Best Practices
- Save checkpoints frequently - Every 30-60 minutes during complex tasks
- Be specific - Include file paths, line numbers, exact findings
- Document decisions - Record why choices were made
- Link related files - Reference other analysis documents
- Include recovery steps - Make resumption easy
Related Commands
- - Load project context
/context - - Manually trigger context compaction
/compact - - Generate progress summary
/watzup
IMPORTANT Task Planning Notes
- Always plan and break many small todo tasks
- Always add a final review todo task to review the works done at the end to find any fix or enhancement needed