strategic-compactlisted

# Strategic Compact Skill Suggests manual `/compact` at strategic points in your workflow rather than relying on arbitrary auto-compaction. ## When to Activate - Running long sessions that show context pressure or degraded coherence - Working on multi-phase tasks (research → plan → implement → test) - Switching between unrelated tasks within the same session - After completing a major milestone and starting new work - When responses slow down or become less coherent (context pressure) ## Why Strategic Compaction? Auto-compaction triggers at arbitrary points: - Often mid-task, losing important context - No awareness of logical task boundaries - Can interrupt complex multi-step operations Strategic compaction at logical boundaries: - **After exploration, before execution** — Compact research context, keep implementation plan - **After completing a milestone** — Fresh start for next phase - **Before major context shifts** — Clear exploration context before different task ## Compaction Decision Guide Use this table to decide when to compact: | Phase Transition | Compact? | Why | | ------------------------- | -------- | --------------------------------------------------------------- | | Research → Planning | Yes | Research context is bulky; plan is the distilled output | | Planning → Implementation | Yes | Plan is in TodoWrite or a file; free up context for code | | Imple