session-management

Maintain session state across Claude Code conversations with structured files and logs.

9|1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/conorbronsdon/claude-code-skills --skill session-management-conorbronsdon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-management
Source: https://github.com/conorbronsdon/claude-code-skills/tree/main/session-management
Command: npx skills add https://github.com/conorbronsdon/claude-code-skills --skill session-management-conorbronsdon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude Code forgets context between sessions, making it easy to lose decisions, drift from priorities, and forget blockers or follow-ups. This Skill creates a lightweight session lifecycle so the project stays coherent across starts, checkpoints, ends, and daily heartbeats.

Core Features & Use Cases

  • Start sessions with a briefing that loads current priorities, recent decisions, blockers, and fresh changes.
  • Checkpoint mid-session, close sessions with automatic summaries, and roll state updates into persistent logs.
  • Run daily heartbeats to flag stale state, surface deadlines, and propose memory updates for approval.
  • Use case: keep a long-running coding project aligned when multiple Claude Code sessions, parallel changes, or handoffs are happening.

Quick Start

Use the session-management skill to set up the state files in your project and then run /start to load context and brief the next session.

Frequently Asked Questions about session-management

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

FAQPage Schema
How do I keep Claude Code state in sync across multiple sessions?

To keep Claude Code state in sync across sessions, use a structured session lifecycle to load current priorities, recent decisions, and blockers at start, then roll state updates into persistent logs during checkpoints and session closures.

Why does Claude Code forget context between conversations?

Claude Code forgets context between conversations because it lacks persistent session state by default, causing decisions, priorities, and blockers to drift. A lightweight session lifecycle with structured state files and session journals prevents this loss.

How do I log decisions and blockers in Claude Code projects?

You log decisions and blockers in Claude Code projects by applying a checkpoint workflow that rolls mid-session updates into a persistent decision log, ensuring follow-ups and blockers are tracked across parallel changes and handoffs.

What's the best way to manage long-running coding projects with parallel Claude Code changes?

The best way to manage long-running coding projects with parallel Claude Code changes is running daily heartbeats to flag stale state, surface deadlines, and propose safe memory updates for approval without silent writes.

Do I need structured state files to maintain session context in Claude Code?

Yes, you need structured state files to maintain session context in Claude Code, as the session lifecycle requires them to store persistent priorities, session journals, and decision logs for accurate briefings and freshness checks.

Can I run a daily heartbeat to flag stale state in Claude Code?

Yes, you can run a daily heartbeat to flag stale state in Claude Code, which surfaces deadlines and proposes memory updates for approval, keeping the project coherent without silent writes to persistent logs.