Strategic Context Compaction FAQs

Question 1

Does this skill run the /compact command automatically?

Accepted Answer

No, it acts as a nudge. It monitors your activity and suggests that you run the command yourself, allowing you to decide if now is the right logical moment.

Question 2

Will I lose my progress if I use the /compact command?

Accepted Answer

Compaction clears intermediate reasoning and tool history, but your files on disk, CLAUDE.md instructions, TodoWrite lists, and git state remain fully intact.

Question 3

Can I customize when the compaction suggestion appears?

Accepted Answer

Yes, you can set the COMPACT_THRESHOLD environment variable to define how many tool calls should occur before the skill suggests a manual compaction.

Question 4

How does strategic compaction differ from auto-compaction?

Accepted Answer

Auto-compaction triggers at arbitrary technical limits, often losing important context mid-task. Strategic compaction suggests manual triggers at logical boundaries, like after a plan is finished but before code writing begins.

Question 5

When is the best time to compact my session context?

Accepted Answer

The best times are after completing a major research phase, after finalizing a plan in a file, or after finishing a long debugging session before starting a new feature.

Strategic Context Compaction

主な機能

ユースケース

Strategic Context Compaction

主な機能

ユースケース