strategic-compact

Manual compaction at logical checkpoints prevents automatic compaction from losing important task state. This Skill monitors tool-call counts via PreToolUse hooks and suggests running /compact at phase boundaries to preserve distilled plans.

A lightweight counter script tracks tool-call activity and emits compaction suggestions when a configurable threshold is reached. It operates on PreToolUse events for Edit and Write actions, displaying inline reminders during active workflows.

Yes, you can configure the compaction threshold using the COMPACT_THRESHOLD environment variable. The Skill also supports periodic reminders after the threshold is reached to accommodate different session lengths and workflows.

You should compact context when transitioning between research, planning, implementation, and testing phases. Compacting at these logical boundaries preserves the distilled plan and relevant files while clearing exploratory reasoning from the context window.

No, the Skill does not perform automatic compaction. It solely tracks tool-call counts and emits suggestions for manual /compact actions, ensuring you retain control over when context is compressed and what state is preserved.

Using strategic manual compaction suggestions is the best way to manage context in high tool-call workflows. By monitoring tool-call counts and suggesting compaction at configured thresholds, you avoid mid-task context loss and maintain task state.