← ClaudeAtlas

context-persistencelisted

Waypoint plans methodology and session survival patterns for Claude Code. Use when working on long-running features, need to resume after context reset, want to document task progress, or need to survive session interruptions. Covers three-file structure (plan/context/tasks), SESSION PROGRESS tracking, quick resume instructions, update frequency, and context handoff patterns.
aiskillstore/marketplace · ★ 329 · Data & Documents · score 79
Install: claude install-skill aiskillstore/marketplace
# Context Persistence Skill ## Purpose Ensure Claude Code can resume work seamlessly after context resets, session interruptions, or long breaks by maintaining structured documentation of current work, decisions, and progress. ## When to Use This Skill Automatically activates when you mention: - Waypoint plans, waypoint planning - Resuming work, continuing work - Session survival, context reset - Task handoff, progress tracking - Long-running features or projects - Need to document current state ## The Problem: Context Resets **What happens during a context reset**: - ❌ All conversation history lost - ❌ Current task context forgotten - ❌ Decisions and rationale gone - ❌ Progress not tracked - ❌ Have to re-explain everything **With context persistence**: - ✅ Current task documented - ✅ Decisions and rationale preserved - ✅ Progress clearly tracked - ✅ Quick resume in < 1 minute - ✅ Seamless handoff to future sessions --- ## Three-File Structure The core pattern uses **three complementary files** in `plans/active/{task-name}/`: ### 1. `{task-name}-plan.md` - The Strategic Plan **Purpose**: High-level strategy and approach **Contains**: - Feature/task overview - Requirements and acceptance criteria - Architecture approach - Implementation phases - Dependencies and constraints - Risks and mitigations **Update frequency**: Rarely (only when approach changes) **Example**: ```markdown # Authentication Implementation Plan ## Overview Add JWT-based authentication to re