strategic-compact

Name: strategic-compact
Availability: InStock
Author: chomchomchomy

Compact session memory at strategic milestones to preserve key decisions.

Updated Aug 23, 2026

Search Tags:#context-management #design-review #memory-optimization #decision-logging #task-organization #compact-memory

Ready to run

npx skills add https://github.com/chomchomchomy/antigravity-skills --skill strategic-compact-chomchomchomy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: strategic-compact
Source: https://github.com/chomchomchomy/antigravity-skills/tree/main/strategic_compact
Command: npx skills add https://github.com/chomchomchomy/antigravity-skills --skill strategic-compact-chomchomchomy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI sessions can run long and risk losing important decisions as context threads expand; Strategic Compact helps by proposing manual memory compacting at key moments to preserve essential context.

Core Features & Use Cases

Proposes compacting at strategic milestones (design complete, major milestone, debugging complete) to discard irrelevant logs and keep only the decision record.
Encourages exporting a reference snapshot (e.g., SUMMARY.md) so decisions and context remain accessible after memory refresh.
Advises ensuring planning is fixed before compacting and maintaining focus on implementation once it is stable.

Quick Start

Summarize the current investigation and compact the context at the next design or milestone, preserving key decisions while discarding nonessential logs.

Frequently Asked Questions about strategic-compact

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent important context from being lost during long AI sessions?▼

To prevent important context from being lost during long AI sessions, apply manual memory compaction at major milestones to discard irrelevant logs and preserve the decision record. This ensures crucial context survives memory refresh.

When should I compact memory to preserve design decisions and context?▼

Compact memory to preserve design decisions at strategic moments such as design completion, major milestones, or after debugging. Compacting at these points discards nonessential logs while keeping the decision record intact for future use.

How do I export a reference snapshot to keep decisions accessible after memory refresh?▼

Export a reference snapshot like SUMMARY.md to keep decisions accessible after memory refresh. This documents the compacted context, ensuring decisions and essential context remain available even after the thread is cleared.

What is the best way to organize tasks and compact context without losing planning details?▼

The best way to compact context without losing planning details is to ensure planning is fixed before compacting. Once planning is stable, compact the context to maintain focus on implementation while preserving the decision record.

Does memory optimization work for end-to-end workflows after debugging is complete?▼

Memory optimization works for end-to-end workflows after debugging by proposing, performing, and documenting the compacted context. This ensures decisions survive the memory refresh and the workflow continues with a clean context.