Skip to main content
Context compression controls how much OpenSpec context is passed to Superpowers during the design→build handoff. It is a beta feature designed to reduce token use without compromising implementation correctness. Unlike traditional summary-based context compression, which condenses the key points and can cause Spec Coding tasks to lose steps or details, Comet preserves spec integrity through structured projection and hash references. That reduces token use without introducing spec drift that can derail downstream Agent execution.

Xiaoyu compares the full off handoff summary with beta mode that preserves delta specs and hashes supporting files

​
Modes

ModeOutputUse when
offFull readable design-context.json/mdYou want maximum context and token cost is acceptable.
betaVerbatim spec projection plus hashes for supporting filesYou want smaller context while preserving spec truth.

​
Why beta keeps specs verbatim

Delta specs are the requirement contract. Compression must not paraphrase or summarize them. Supporting files can be referenced by path and hash when their exact content is not needed in the next prompt.

​
Drift handling

Handoff files include source paths and hashes. Guards can detect when source artifacts changed and require handoff regeneration.

​
Next steps

Last modified on July 3, 2026