strategic-compact

Prompt manual context compaction at phase transitions in long multi-phase sessions.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/KanakMalpani/General-Private-Skills --skill strategic-compact-kanakmalpani
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strategic-compact
Source: https://github.com/KanakMalpani/General-Private-Skills/tree/main/skills/strategic-compact
Command: npx skills add https://github.com/KanakMalpani/General-Private-Skills --skill strategic-compact-kanakmalpani

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill reduces context loss by guiding users to manually compact context at logical boundaries rather than relying on automatic, arbitrary auto-compaction.

Core Features & Use Cases

  • Guidance for timing compacting at phase transitions (research → planning, planning → implementation, milestones)
  • A configurable hook setup that integrates with workflow tools to prompt when to compact
  • Use cases include long-running sessions, multi-phase projects, and multi-task sessions where context grows

Quick Start

Run the /compact command at logical phase transitions to preserve context.

Frequently Asked Questions about strategic-compact

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

FAQPage Schema
How do I prevent context loss during long multi-phase coding sessions?

Manual context compaction at logical phase boundaries prevents context loss by preserving coherence across research, planning, execution, and review milestones. Running /compact at transitions triggers threshold-based prompts to save session state.

When should I manually compact context instead of relying on auto-compaction?

Manual compaction is needed at phase transitions like research to planning, or planning to implementation, where switching contexts or approaching milestones occurs. It provides deterministic workflow guidance rather than arbitrary auto-compaction cutoffs.

How do I set up hooks to prompt context compaction at workflow milestones?

Configurable hook setup integrates with workflow tools to prompt when to compact. Optional scripting supports deterministic guidance, applying threshold-based prompts during multi-phase projects to maintain context across milestones.

Does manual context compaction work for multi-task sessions with growing context windows?

Manual context compaction suits multi-task sessions where context grows continuously. By guiding users to compact at logical boundaries rather than arbitrary limits, it preserves coherence for long-running sessions and multi-phase projects.

What are the limitations of relying on automatic compaction for multi-phase projects?

Automatic compaction risks context loss by cutting off at arbitrary limits rather than logical boundaries. Without phase-aware compaction, multi-phase projects lose coherence when switching contexts or reaching milestones during execution and review.