context-preservation

Preserve and restore session context using timestamped context files.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/I2olanD/dotfiles --skill context-preservation-i2oland
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-preservation
Source: https://github.com/I2olanD/dotfiles/tree/main/.config/opencode/skill/context-preservation
Command: npx skills add https://github.com/I2olanD/dotfiles --skill context-preservation-i2oland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preserve and restore session context across conversations to maintain continuity of work. This skill ensures decisions, progress, blockers, and discoveries are captured and can be handed off between sessions.

Core Features & Use Cases

  • Capture decisions, progress, blockers, and discoveries to enable seamless handoff between sessions.
  • Restore exact context at resume time, load the active context, and guide next steps.
  • End-of-session capture and restoration workflows to prevent loss of work.

Quick Start

Activate this skill at the end of a session to save the current context to .config/opencode/context, then restore it in a new session using the "Continue from context" flow.

Frequently Asked Questions about context-preservation

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

FAQPage Schema
How do I preserve session context across conversations?

To preserve session context, activate the skill at the end of a session to capture decisions, progress, blockers, and discoveries into timestamped context files for seamless handoff.

What is the best way to resume work after switching contexts?

The best way to resume work is to use the Continue from context flow, which loads the active context file and guides your next steps to restore exact context.

Can I save session progress and blockers to context files?

Yes, you can save session progress and blockers. The skill enforces a structured context format to capture decisions, progress, blockers, and discoveries into timestamped context files.

Does session tracking work without external dependencies?

Yes, session tracking works without external dependencies. The skill operates independently to capture and restore work continuity using structured context files.

When do I need to capture session context for a work handoff?

You need to capture session context when completing significant work, switching contexts, or resuming prior sessions, ensuring work continuity and preventing loss of progress.

Why does restoring context prevent loss of work?

Restoring context prevents loss of work by loading the active context file at resume time, which carries forward documented decisions, blockers, and discoveries from the previous session.