strategic-compact

Prevent context loss by prompting manual /compact at logical phase boundaries, preserving task context between research and implementation phases instead of relying on automatic compaction.

Run /compact after exploration phases, before implementation, or upon milestone completion to retain long-term memory and ensure the next phase starts with a clean, preserved context.

Yes, the context-tracking mechanism combines PreToolUse hooks with tool call tracking to monitor workflow progress and remind you when manual /compact is appropriate at logical boundaries.

It is best suited for multi-phase workflows alternating between research and implementation, where milestones and long-term memory retention require strategic compaction at phase boundaries.

Customize compaction thresholds using environment variables and configuration files, allowing the context-tracking mechanism to adapt reminders across various multi-phase workflow environments.

Manual /compact at logical phase boundaries preserves critical task context by timing compaction strategically, whereas automatic compaction may discard important details at inconvenient workflow points.