CtrlK
BlogDocsLog inGet started
Tessl Logo

session-checkpoints

Saves and restores session state including task progress, file changes, and delegation history. Use when saving progress, resuming interrupted work, picking up where you left off, or checkpointing current work.

100

Quality

100%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Skill: Session Checkpoints

When to Checkpoint

TriggerAction
Before first delegationAfter decomposition, before agents start
After each phaseWhen a parallel batch completes
Before risky workDB migrations, large refactors, security changes
Session endAny session with incomplete work
Context running lowCheckpoint immediately

Checkpoint Template

The full checkpoint template has been moved to CHECKPOINT-TEMPLATE.md in this directory for progressive disclosure. Use that file as the canonical, copy-pasteable checkpoint document.

See the Decomposition Flow in the decomposition skill for when to create checkpoints: decomposition.

Checkpoint creation (quick)

  1. Create .opencastle/SESSION-CHECKPOINT.md from the example below.
  2. Commit checkpoint or save to workspace and attach to the tracker issue.
  3. Verify: cat .opencastle/SESSION-CHECKPOINT.md and confirm listed files exist.
# Session Checkpoint — 2026-04-01

## Summary
Implementing search filters — unit tests passing, E2E pending.

## Files Touched
- src/components/SearchFilter.tsx (new)
- src/hooks/useFilters.ts (modified)

## Task Status
| Task | Status |
|------|--------|
| TASK-12 Search filter component | Done |
| TASK-13 E2E filter tests | In Progress |

## Resume Instructions
1. Run `git checkout feat/search-filters`
2. Start dev server: `pnpm dev`
3. Continue TASK-13: write E2E tests for filter interactions

For the complete copy-pasteable template, see CHECKPOINT-TEMPLATE.md.

Resuming

  1. Read .opencastle/SESSION-CHECKPOINT.md
  2. Run git status and git branch — confirm you are on the correct branch
  3. Check In Progress tasks — if stale (>1 session old), verify files match expected state
  4. Check Pending Approvals — remove rows for questions answered via VS Code chat
  5. Read tracker issues for any tasks marked In Progress or Todo
  6. Follow the Resume Instructions section in the checkpoint
  7. Update checkpoint progress after each completed task

If checkpoint is missing or corrupt: Rebuild from git log --oneline -20 and tracker state.

Cleanup & Team Lead

When all issues Done: archive to tracker, delete .opencastle/SESSION-CHECKPOINT.md.

Repository
monkilabs/opencastle
Commit

f5c8508

Last updated
Created

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.

Claim skill