strategic-compact

Manage manual context compaction at strategic workflow phase transitions.

1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/samChang72/custom-skills --skill strategic-compact-samchang72
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strategic-compact
Source: https://github.com/samChang72/custom-skills/tree/main/claude-config/skills/strategic-compact
Command: npx skills add https://github.com/samChang72/custom-skills --skill strategic-compact-samchang72

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Prevents loss of context during task transitions, ensuring that key information is retained and not lost during arbitrary auto-compaction.

Core Features & Use Cases

  • Manual Context Compaction: Allows users to trigger context compaction at strategic points in the workflow, maintaining context through different phases.
  • Strategic Points: Suggestions for compaction are made after exploration, before execution, and at milestones, enhancing workflow efficiency.
  • Use Case: When working on complex projects, this Skill can help maintain context, reducing errors and enhancing overall productivity.

Quick Start

Use the command /compact to manually compact context when transitioning between different phases of your project.

Frequently Asked Questions about strategic-compact

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

FAQPage Schema
How do I preserve AI context when transitioning between project phases?

To preserve AI context during task transitions, trigger manual context compaction at strategic workflow points using the /compact command, ensuring key research and planning details survive execution phases.

Why does auto-compaction lose critical information during complex coding workflows?

Auto-compaction loses critical information because it triggers arbitrarily rather than at logical milestones. Manual context compaction solves this by letting you strategically retain key details before execution phases.

When should I manually compact context in a research or planning workflow?

You should manually compact context after exploration, before execution, and at project milestones. Triggering compaction at these strategic points maintains context integrity across complex task transitions.

What is the best way to maintain context integrity for multi-step coding tasks?

The best way to maintain context integrity for multi-step coding tasks is manual context compaction at strategic workflow points, preventing arbitrary auto-compaction from dropping essential planning details.

Can I use manual context compaction for strategic planning and research tasks?

Yes, you can use manual context compaction for strategic planning and research tasks. It optimizes workflow transitions by preserving key information through different project phases.

Do I need dependencies to trigger context compaction at workflow milestones?

No dependencies are required to trigger context compaction. The Skill operates standalone, allowing you to manually compact context at workflow milestones directly using the /compact command.