Agent skill · software engineering · sickn33
cc-skill-strategic-compact
Prepare a verified checkpoint before condensing an agent conversation at a phase boundary. Use during long tasks when context is repetitive; preserves constraints, evidence, decisions and the next action.
Why this skill is useful
This skill does not provide any specific actionable knowledge or scripts beyond general development practices.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Strategic Context Checkpoints Condense context after a verified phase, with enough durable information to resume the same task. A tool-call count is only a reminder; it cannot measure context quality or decide when compaction is safe. When to Use Use when exploration has finished, a tested milestone has landed, or a long conversation contains repeated or obsolete reasoning. Do not compact in the middle of an unresolved tool call, an unrecorded approval decision, or a failure whose exact evidence has not been captured. Inputs and prerequisites The user's current objective, accepted constraints and definition of done. The current branch and source revision, local changes, relevant artifact paths and actual check results. Running processes, pending tool calls, approvals or external blockers. A host-supported context-compaction mechanism. This skill does not assume /compact exists in every client or manipulate internal context files. Procedure 1. Choose a phase boundary: discovery to implementation, implementation to verification, or one completed batch to the next. Preserve an unresolved failure's reproduction first. 2. Reconcile task state with the filesystem and Git. Distinguish completed, uncommitted, planned and failed work. 3. Produce the checkpoint below. Include exact commands, result summaries and paths needed to resume; omit copied logs and discarded hypotheses that no longer matter. 4. Check that the next action is executable and that a new context would not repeat a merge, send a message twice, lose a constraint or overwrite unrelated work. 5. Save only in an already authorized project artifact, or return the checkpoint in the conversation. Do not rewrite global memory or host configuration automatically. 6. Use the client's supported compaction command if requested and available. On resumption, read the checkpoint and verify mutable state before continuing. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/cc-skill-strategic-compact--e171ad