Overview

Before switching to a different task, write a context file documenting progress, next steps, and lessons learned.

The Context Switch Problem

Task switching without documentation causes: - Lost insights discovered during work - Repeated mistakes - Wasted time re-orienting - Forgotten constraints

The Protocol

Before Switching

1. Create context file: memory/task-<name>.md
2. Document status, discoveries, next steps
3. Link from NOW.md
4. Clear working memory

After Switching Back

1. Read context file
2. Review discoveries
3. Update context
4. Continue work

Context File Template

```markdown

Task: [Name]

Status

[Where you left off]

What Worked

• Approach A: [result]

What Didn't Work

• Approach X: [why it failed]

Next Steps

1. [Priority 1]
2. [Priority 2]

Constraints Discovered

• [Constraint 1]

Key Insights

• [Insight 1] ```

When to Use

Use for: - Multi-day projects - Interrupt-driven work - Parallel tasks

Skip for: - Quick one-off queries - Trivial tasks (< 5 minutes)