Session Memory

Overview

Persist workflow state to survive context compaction. Files in .claude/cc10x/session/ outlive the context window.

Core principle: Write often, read on resume, never lose progress.

On Any Workflow Start

1. Check: Does `.claude/cc10x/session/current-task.md` exist?
2. If YES:
   - Read current-task.md and progress.md
   - Ask: "Found in-progress task: [task]. Resume or start fresh?"
3. If NO:
   - Create current-task.md with new task
   - Continue with workflow

After Each Significant Action

Write to .claude/cc10x/session/progress.md:

## Progress
**Task:** [what we're building/reviewing/debugging]
**Phase:** [current phase name]
**Completed:**
- [done item 1]
- [done item 2]
**Next:** [immediate next step]
**Updated:** [timestamp]

On Key Decisions

Append to .claude/cc10x/session/decisions.md:

## [timestamp]
**Decision:** [what was decided]
**Reason:** [why]
**Impact:** [what this affects]

On Task Completion

1. Clear `.claude/cc10x/session/current-task.md`
2. Optionally archive to `.claude/cc10x/artifacts/`
3. Update `.claude/cc10x/memory/patterns.md` if learned something reusable

Folder Structure

.claude/cc10x/
├── session/           # Current workflow state
│   ├── current-task.md
│   ├── progress.md
│   └── decisions.md
├── memory/            # Long-term learnings
│   └── patterns.md
└── artifacts/         # Workflow outputs
    └── [archived outputs]

When Context Gets Full

Before compaction happens:

1. Ensure progress.md is current
2. Write any critical context to session/context.md
3. After compaction, this skill re-reads and announces state

This is why we survive compaction - files persist, context doesn't.