cc-skill-strategic-compact

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 dis