strategic-compact

Prevent context loss by suggesting manual /compact checkpoints at meaningful phase boundaries. This approach preserves critical research, planning, and implementation context by prompting compaction before auto-compaction removes important information at arbitrary times.

Run /compact manually during logical workflow transitions, such as moving from research to planning or implementation to testing. A hook-driven counter suggests compaction after a configurable number of tool calls to avoid mid-implementation context loss.

A deterministic hook-driven counter tracks tool calls and suggests manual compaction once a configurable threshold is reached. It then continues emitting reminders at regular checkpoints, aligning context management with workflow phase transitions.

Yes, the Skill entrypoint supports configurable tool-call thresholds and encourages compaction at research to plan, plan to implementation, and testing milestone boundaries. This ensures phase context is preserved while avoiding mid-implementation information loss.

Strategic compaction solves session incoherence and unexpected context limits during multi-phase feature builds. By suggesting compaction at logical milestones rather than random timing, it preserves the correct phase context needed to start the next workflow stage cleanly.

Yes, strategic compact operates as a standalone hook with no external dependencies. It uses a script component to monitor tool calls and emit compaction reminders, requiring only the Claude environment to function.