session-state

Persist session memory to the .ccu directory across AI sessions.

1|Updated Feb 3, 2026

Search Tags:#memory #evidence #handoff #session #artifact #crash-recovery #ccu

Ready to run

npx skills add https://github.com/trungtnm/claude-code-utils --skill session-state-trungtnm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-state
Source: https://github.com/trungtnm/claude-code-utils/tree/main/plugins/skills/session-state
Command: npx skills add https://github.com/trungtnm/claude-code-utils --skill session-state-trungtnm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The session-state skill externalizes project session memory to the .ccu directory to maintain continuity across AI sessions, enabling evidence logging, decisions tracking, and crash recovery.

Core Features & Use Cases

Persistence of session context: stores ephemeral and persistent artifacts to bridge between runs.
Crash recovery & handoffs: provides a stable memory layer to resume work after interruptions and hand off context between sessions.
Governance of decisions and evidence: centralizes records of decisions, evidence, and planned next steps for audit and collaboration.

Quick Start

Initialize the .ccu directory and create starter state files for the current project session.

Frequently Asked Questions about session-state

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

FAQPage Schema

How do I maintain persistent session memory across AI coding sessions?▼

To maintain persistent session memory across AI coding sessions, you can externalize state to a dedicated directory. This skill coordinates files like SESSION.md and CHECKPOINT.md to bridge context between runs.

What is the best way to recover project context after an AI session crash?▼

Recovering project context after a crash requires a stable memory layer like CHECKPOINT.md. This skill safely reads missing state files and allows active commands to write recovered data for seamless resumption.

How do I hand off session state to another developer or AI agent?▼

Handing off session state involves writing context to a shared file like HANDOFF.md. This skill centralizes planned next steps and decision records, ensuring the receiving agent understands the current project status.

Can I track decisions and evidence logs within my project directory?▼

Yes, you can track decisions and evidence logs by storing them in dedicated files like DECISIONS.md and EVIDENCE.md. This skill centralizes these artifacts for audit, governance, and collaboration.

Do I need any specific dependencies to externalize my session state?▼

No specific dependencies are required to externalize session state. This skill operates independently, reading state safely when files are missing and ensuring writes are handled by the active command.

When should I avoid using file-based externalization for session memory?▼

You should avoid file-based externalization if your workflow requires real-time concurrent editing rather than sequential command writes. This skill maintains stability by ensuring only the active command writes state.