session-memory

Create structured session files to preserve and resume coding sessions.

Updated May 29, 2026
One-click install
npx skills add https://github.com/rblake2320/vigil --skill session-memory-rblake2320
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-memory
Source: https://github.com/rblake2320/vigil/tree/main/.claude/skills/session-memory
Command: npx skills add https://github.com/rblake2320/vigil --skill session-memory-rblake2320

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Durable, human-readable session records enable seamless resumption of coding work after disconnects, restarts, or handoffs.

Core Features & Use Cases

  • Create a per-session working directory with structured files (session_state.md, timeline.md, files.md, handoff.md) to capture goals, progress, and decisions.
  • Support checkpointing and continuity across long-running tasks, disconnections, or branch switches.
  • Facilitate smooth handoffs between agents by providing an up-to-date, queryable record of context and plan.

Quick Start

Create a new timestamped session directory and begin populating the standard files to capture goals, plan, and next actions.

Frequently Asked Questions about session-memory

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

FAQPage Schema
How do I preserve coding agent context across VS Code restarts?

Preserve coding context across restarts by creating a timestamped session directory with structured markdown files like session_state.md and timeline.md to capture goals, progress, and decisions for seamless resumption.

What is the best way to hand off a long-running coding session to another agent?

Hand off long-running coding sessions by writing an up-to-date handoff.md file alongside timeline.md and files.md, providing the next agent a queryable record of context, plan, and next actions for smooth continuity.

How do I checkpoint workflow progress during long-running coding tasks?

Checkpoint workflow progress by writing current state to structured session files after planning phases, during edits, and at regular intervals, ensuring durable records exist for later resumption.

Do I need any external dependencies to maintain session memory for coding agents?

No external dependencies are required. The approach relies solely on creating a session directory populated with human-readable markdown files to store state, timeline, and handoff information.

When should I use structured session files for state management instead of other coding agent tools?

Use structured session files for state management during disconnections, branch switches, or agent handoffs where a durable, human-readable record is needed to seamlessly resume long-running workflows.