strategic-compact

Strategic context compaction prevents context loss by prompting manual compaction at logical task phase transitions rather than relying on automatic compaction. It tracks tool invocations and prompts you at configurable thresholds to preserve critical planning details before major workflow shifts.

The best way to manage token limits before major context shifts is to trigger manual context compaction at strategic workflow points. This preserves essential planning notes and session integrity while clearing out exploration details before moving to execution phases.

You should manually compact context at strategic task phase transitions, such as after completing a research phase before starting implementation. This ensures important exploration information is retained and prevents mid-task context loss that automatic compaction might cause.

Context compaction for session integrity works by tracking tool invocations throughout long-running sessions and prompting you to compact at configurable thresholds. This preserves the core plan while clearing exploration details when transitioning between task phases.

Yes, you need to configure thresholds for context management in sessions with high tool call counts. The skill requires tracking tool invocations and prompting you at these set thresholds to maintain session integrity and suggest manual compaction at strategic workflow points.