memory-management

name	Memory Management
description	Context hygiene, memory flush before compaction, sub-agent lifecycle, and daily operations patterns. Use when: Context is growing large and you need to prepare for compaction, switching between unrelated tasks, or establishing a daily operations routine. Also use when spawning sub-agents for long tasks. Don't use when: Debugging a specific issue (use the appropriate troubleshooting skill). Don't use for deploying changes (use gitops-deploy). This is an internal operations pattern, not a diagnostic tool. Outputs: No external artifacts. This skill guides internal behavior — writing to workspace files, spawning sub-agents, and managing context.
requires	[]

Memory Management

Routing

Use This Skill When

• Context window is getting large and compaction is approaching
• Switching from one task to a completely different topic
• Starting a new session and need to reload context
• Spawning a sub-agent for a long-running task
• Need to persist important findings before they're compacted away

Don't Use This Skill When

• Debugging a pod, Flux, or CI issue → use the specific skill
• Deploying changes → use gitops-deploy
• Reviewing sessions → use session-review (robert)
• This is about managing YOUR OWN context, not the user's data

Context Hygiene

Before Starting a New Task

Run /compact to clear stale context before switching topics. This prevents hallucination from prior task context bleeding into the new one.

After Configuring Something

Commit important details to memory immediately. Verify by repeating the key facts back. Don't rely on session context surviving — compaction or restarts will lose it.