skill-resume-enhanced

Reload persistent project state and decisions from state.json after context resets.

4.0k|369|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/nyldn/claude-octopus --skill skill-resume-enhanced
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-resume-enhanced
Source: https://github.com/nyldn/claude-octopus/tree/main/skills/skill-resume-enhanced
Command: npx skills add https://github.com/nyldn/claude-octopus --skill skill-resume-enhanced

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persistent session state across context-clearing events (e.g., native plan mode) so work can resume without loss, across days.

Core Features & Use Cases

  • State persistence in files (.claude-octopus/state.json) and per-phase context to enable resumption after context clears.
  • Automatic detection of context clearing and loading prior sessions, including decisions, tasks, and metrics.
  • Multi-day project continuity with session naming, task restoration, and history replay to ensure seamless progression.

Quick Start

Ask to resume the last Octopus session to reload prior context from persistent state.

Frequently Asked Questions about skill-resume-enhanced

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

FAQPage Schema
How do I restore project context and decisions after a plan-mode reset clears my session?

To restore project context after a plan-mode reset, persistent session state is reloaded from stored files, rehydrating prior phase context, decisions, and task lists to enable automatic resume and continuity.

Can I resume a multi-day project session without losing my previous task history?

Multi-day project continuity is supported by persisting session metadata, task lists, and decisions in files, allowing you to resume work and replay history seamlessly across days without losing prior progress.

How does persistent session state work for reloading prior project decisions?

Persistent session state works by saving project context, decisions, and tasks into a state.json file and per-phase storage, which is automatically detected and loaded to rehydrate the session after context clears.

Does this session resume approach require specific dependencies or external tools to function?

No external dependencies or tools are required to function. The session resume mechanism relies entirely on internal persistent storage files to detect context clearing and reload prior session state.

What is the best way to maintain workflow continuity across context-clearing events in software engineering?

The best way to maintain workflow continuity is using persistent state files that automatically detect context-clearing events, loading prior session metadata and tasks to rehydrate the project environment without manual intervention.

Why does my project context disappear after interacting with native plan mode, and how can I prevent loss?

Project context disappears because native plan mode clears the session environment. You prevent loss by persisting state and decisions in files beforehand, enabling automatic detection and reloading of the prior session.