strategic-compact

Compress task context manually at logical boundaries between planning and execution.

24|5|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/Luohaothu/everything-codex --skill strategic-compact-luohaothu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: strategic-compact
Source: https://github.com/Luohaothu/everything-codex/tree/main/docs/zh-CN/skills/strategic-compact
Command: npx skills add https://github.com/Luohaothu/everything-codex --skill strategic-compact-luohaothu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

在任务探索与执行之间,关键上下文易在无意中被压缩或遗失。本技能提供在逻辑边界处进行手动上下文压缩的机制,以确保后续阶段保留必要信息。

Core Features & Use Cases

  • 手动压缩点:在计划与执行阶段之间执行上下文压缩,保留实现所需的关键信息。
  • 阈值驱动提示:具备可配置的阈值,在达到阈值时提示进行压缩以避免信息丢失。
  • 场景示例:在完成一个里程碑后进行上下文压缩,以便从新阶段开始并保持连贯性。

Quick Start

将策略节点应用于工作流,按配置的阈值与 PreToolUse 钩子执行手动上下文压缩。

Frequently Asked Questions about strategic-compact

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

FAQPage Schema
How do I preserve task context when moving from planning to execution?▼

To preserve task context at workflow boundaries, you can manually compress context at logical milestones. This ensures crucial information is retained for stable hand-offs between exploration, planning, and execution phases.

What triggers a manual context compression during a multi-step workflow?▼

A threshold-based trigger and a PreToolUse hook prompt manual context compression. When the configured threshold is reached, the mechanism initiates to prevent unintentional information loss across task phases.

How do I apply manual context compression at workflow boundaries?▼

You apply strategic nodes within your workflow to execute manual context compression based on configured thresholds and a PreToolUse hook. This preserves necessary information before starting a new phase.

When should I compress context to avoid losing crucial task information?▼

You should compress context when reaching a logical boundary or completing a milestone within multi-step tasks. This prevents crucial context from being inadvertently compressed or lost before starting subsequent phases.

Do I need any specific dependencies to use threshold-based context compression?▼

No specific dependencies are required to implement threshold-based context compression. The mechanism operates independently using a lightweight manual-compression workflow triggered by a PreToolUse hook.

What is the best way to maintain context continuity across multi-step tasks?▼

The best way to maintain context continuity is by applying manual compression at logical workflow boundaries. This threshold-driven approach ensures stable hand-offs and retains execution-required information across phases.