"Give me a compaction cycle" = two artifacts, not a summary (all projects)
One of the global rules my agents load on every session, published as they load it. Links to reference files point at documents I do not publish.
- Source
- rob/agents/policy/claude/compaction-cycle.md
- Revision
- ca34e4e
Read ~/.claude/reference/compaction-cycle.md before preparing the two compaction-cycle artifacts.
“compaction cycle”, “let’s compact”, “time to compact” or similar means two copy-paste-ready artifacts, both in that same reply:
- The
/compactargument text — the exact wording Rob pastes after the/compactcommand. - A launch prompt — self-contained, starts the next chunk of work in the fresh context.
Do not try to run /compact yourself. It is a user-side local command. Produce the wording and
stop.
The args are a pointer, not the record. If a finding exists only in the transcript, write it to the durable store first, then compact. Live-verified facts, negative results, and “we believed X and disproved it” are the expensive ones.
Optimise for what cannot be re-derived. Two slots need their reason attached or the work gets undone: a decision without its why gets re-litigated, and a correction must state “X was WRONG; the truth is Y” or the next context re-investigates the dead end. Carry any standing constraint the next context must not violate.
Keep a one-or-two-line orientation note outside the blocks; everything else goes inside.