wind-down

Persist session progress and task state before context compaction.

12|2|Updated Jun 8, 2026

Search Tags:#checkpointing #git commit #task completion #session state #context compaction #tracking logs

Ready to run

npx skills add https://github.com/Loringtonian/second-brain-template --skill wind-down

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wind-down
Source: https://github.com/Loringtonian/second-brain-template/tree/main/.claude/skills/wind-down
Command: npx skills add https://github.com/Loringtonian/second-brain-template --skill wind-down

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents lost work by capturing what happened in the current session before context compaction or the end of a task. It helps an AI agent close out work cleanly so the next run can resume from the right place.

Core Features & Use Cases

Checkpointing: Records in-progress state when a session is about to compact or pause.
Task Completion Cleanup: Marks work complete, updates tracking docs, and clears lingering in-progress context.
Git-Safe Persistence: Commits only the files touched in the session so changes are preserved without overcommitting unrelated work.
Use Case: A coding agent finishes a batch of edits, saves the current status in the project logs, and creates a checkpoint commit so the next session can continue immediately.

Quick Start

Tell the assistant to wind down the session and save progress before you stop.

Frequently Asked Questions about wind-down

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

FAQPage Schema

How do I save Claude Code session state before context compaction?▼

You can checkpoint your session state by recording in-progress task status and updating tracking logs before pausing. This captures current work progress so the next session can resume immediately from the exact point where context was compacted.

What is the best way to commit only touched files when finishing a coding session?▼

The best way to commit only touched files is using git-safe persistence, which identifies and commits only the files modified during the current coding session. This preserves your changes cleanly without overcommitting unrelated work from other tasks.

How does task completion cleanup work for AI coding agents?▼

Task completion cleanup for AI coding agents involves marking work complete, updating tracking documents, and clearing lingering in-progress context. This ensures project logs reflect the actual finished state and no stale tasks remain in the session.

Do I need tracking logs and todo files to checkpoint my coding session?▼

Yes, tracking logs and todo files are required to effectively checkpoint your coding session. The checkpointing process applies to Claude Code workflows that update session records and status documents to preserve continuity across runs.

Can I recover session progress after context compaction in Claude Code?▼

Yes, you can recover session progress after context compaction if you saved session state beforehand. By checkpointing progress and committing touched files, the next session reads the orientation context and resumes from the saved tracking logs.

When should I not use a wind-down checkpoint for my project?▼

You should not use a wind-down checkpoint if your workflow lacks tracking logs or status documents to update. Without these session records and orientation context, there is no persistent state to capture for the next run.