session-checkpoints
Saves, restores session state including task progress, file changes, delegation history. Use when saving progress, resuming interrupted work, picking up where you left off, or checkpointing current work.
67
81%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Skill: Session Checkpoints
When to Checkpoint
| Trigger | Action |
|---|---|
| Before first delegation | After decomposition, before agents start |
| After each phase | When a parallel batch completes |
| Before risky work | DB migrations, large refactors, security changes |
| Session end | Any session with incomplete work |
| Context running low | Checkpoint immediately |
Phase boundaries that warrant a checkpoint: see decomposition.
Creating a Checkpoint
- Write
.opencastle/SESSION-CHECKPOINT.mdfrom the canonical CHECKPOINT-TEMPLATE.md. - Commit it or save to workspace; attach to the tracker issue.
- Verify:
cat .opencastle/SESSION-CHECKPOINT.md; confirm listed files exist.
Resuming
- Read
.opencastle/SESSION-CHECKPOINT.md - Run
git status,git branch— confirm you are on correct branch - Check In Progress tasks — if stale (>1 session old), verify files match expected state
- Check Pending Approvals — remove rows for questions answered via VS Code chat
- Read tracker issues for tasks marked In Progress or Todo
- Follow Resume Instructions section in checkpoint
- Update checkpoint progress after each completed task
If checkpoint missing or corrupt: Rebuild from git log --oneline -20, tracker state.
Cleanup & Team Lead
When all issues Done: archive to tracker; delete .opencastle/SESSION-CHECKPOINT.md.
- Repository
- monkilabs/opencastle
- Commit
fa0c341
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.