session-continuity

What problem does it solve?

This skill addresses the challenge of losing task continuity across chat sessions by enforcing a persistent, state-driven workflow. Every message must announce the current state and progress, ensuring you can resume seamlessly after interruptions.

Core Features & Use Cases

• State-driven communication: every interaction prefixes messages with the current state, enabling clear traceability.
• Multi-session continuity: uses the .claude/ directory to persist session state across restarts.
• Deterministic progression: defines a controlled set of states (CHECK_STATUS, WORKING, VERIFY, COMPLETE, BLOCKED, etc.) to guide task execution and verification.
• Safety and control: disallows automatic advancement or ad-hoc actions like TodoWrite to preserve explicit user control.
• Use case example: a long-running data-cleaning task that spans multiple chat sessions, where you gradually implement, verify, and commit changes while maintaining context.

Quick Start

Start a new multi-session task and begin communicating with explicit state prefixes. For example, begin with CHECK_STATUS to establish the current session state, then proceed to WORKING, VERIFY, and COMPLETE as the task progresses.