strategic-compact

Guide session context compression decisions after milestones or 70% token usage.

2|1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/TeamSPWK/nova --skill strategic-compact-teamspwk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strategic-compact
Source: https://github.com/TeamSPWK/nova/tree/main/.claude/skills/strategic-compact
Command: npx skills add https://github.com/TeamSPWK/nova --skill strategic-compact-teamspwk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Strategic-compact provides guidance on the optimal moment to compress the session context by advising whether to perform a session-level /compact or /clear action, ensuring context quality without sacrificing essential information.

Core Features & Use Cases

  • MUST TRIGGER awareness: after completing milestones such as /nova:plan, /nova:design, or /nova:auto, or when token usage reaches 70%, guide the appropriate compression action.
  • Clear separation of levels: distinguish between state-level trimming (NOVA-STATE) and session-level trimming, preventing accidental data loss and preserving critical context.
  • Human-in-the-loop control: the guidance is advisory and non-automatic; the user makes the final decision to execute /compact or /clear.
  • Safety and governance: prevents compression during sensitive phases (e.g., during evaluation) to maintain traceability and debugability.

Quick Start

After a milestone completes or token usage hits 70%, follow this guidance to decide between /compact and /clear for the session context.

Frequently Asked Questions about strategic-compact

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

FAQPage Schema
When should I compact or clear session context to avoid losing critical information?

You should trigger context compression guidance after completing milestones such as plan, design, or auto-execution, or when token usage reaches 70%. This ensures context quality without sacrificing essential information.

How do I safely compress session context without losing state data?

Safely compress session context by enforcing a clear separation between state-level trimming and session-level trimming. This distinction prevents accidental data loss and preserves critical context during compression actions.

Does context compression auto-execute when token usage hits 70%?

No, context compression does not auto-execute when token usage hits 70%. The system enforces human-in-the-loop control, providing advisory guidance so the user makes the final decision to execute compact or clear actions.

Why should I avoid compacting session context during evaluation phases?

Avoid compacting session context during evaluation phases to maintain traceability and debugability. Governance rules prevent compression during sensitive phases to ensure critical context remains available for tracing and debugging.

What is the difference between session-level compact and state-level trimming?

Session-level compact reduces the overall conversation context window, while state-level trimming targets specific state data like NOVA-STATE. Distinguishing these levels prevents accidental data loss and preserves critical context during compression.

Can I use context rotation guidance after finishing a design milestone?

Yes, context rotation guidance specifically triggers after completing milestones such as plan, design, or auto-execution. It advises whether to perform a session-level compact or clear action to enable safe continuation of work.