strategic-compact

Preventing context loss during automated workflow transitions requires prompting manual context compaction at logical milestones. Tracking tool invocation counts identifies strategic boundaries like exploration-to-execution shifts, preserving important information before arbitrary auto-compaction can discard it.

Milestone-based context compaction is prompting context preservation at logical task boundaries rather than arbitrary limits. Use it when transitioning between exploration and execution phases or completing milestones, ensuring critical information survives across task phases in long workflows.

Configuring a threshold for context compaction reminders involves setting a COMPACT_THRESHOLD value that tracks tool invocations. After crossing this threshold, periodic reminders prompt manual compaction via a PreToolUse hook executing the suggest-compact script.

Integrating context compaction prompts with PreToolUse hooks is fully supported. The hook invokes the suggest-compact script, which monitors tool usage counts and triggers manual compaction suggestions once the configured threshold is crossed.

Manual context compaction works without external dependencies. The skill relies solely on its internal scripts to track tool invocations and trigger suggestions through PreToolUse hooks, requiring no additional packages or external libraries to function.

Auto-compaction loses important information across task phases because it triggers at arbitrary limits rather than logical boundaries. Manual compaction at milestone transitions preserves context by targeting natural breakpoints between exploration and execution stages.