Skip to content

yeaight7/agent-powerups / plugins/dev-vitals/skills/strategic-context-compaction

strategic-context-compaction

Verified

Use when deciding whether to compact agent context -- the window is filling up, you are about to switch from one phase to another (research, planning, implementation, debugging), a failed approach left dead-end reasoning, or a previous mid-task compaction lost critical state.

Purpose

Compact at logical boundaries to preserve high-value context while clearing noise. Arbitrary or mid-task compaction loses critical state -- file paths, variable names, partial reasoning -- that is expensive to reconstruct.

When to Use

  • The context window is filling and you are at a phase boundary (research, planning, implementation, debugging)
  • A failed approach left dead-end reasoning that pollutes the next attempt
  • You are starting a conceptually distinct task in the same session
  • A prior mid-task compaction dropped state you then had to rebuild

Inputs

  • The current session state and which phase transition is approaching
  • Knowledge of what is already saved durably (task list, files, git, memory) versus only in conversation

Workflow

  1. Decide whether to compact by transition. Use the boundary table; default to NOT compacting mid-work.

    TransitionCompact?Reason
    Research -- PlanningYesResearch context is bulky; the plan is the distilled output
    Planning -- ImplementationYesPlan is saved in tasks/files; context is free to reset
    Implementation -- TestingMaybeKeep if tests reference recent code; compact if switching focus area
    Debugging -- Next featureYesDebug traces pollute unrelated work
    Mid-implementationNoLosing file paths, variable names, partial state is costly
    After a failed approachYesClear dead-end reasoning before trying a new approach
  2. Save anything you cannot reconstruct cheaply before compacting.

    • Write the plan to a task list or file before compacting after research
    • Commit or stash work-in-progress code before compacting after debugging
    • Note key file paths in the next prompt if they will be needed again
  3. Know what survives versus what is lost. Anything in the Lost column must be persisted in step 2 first.

    SurvivesLost
    CLAUDE.md / AGENTS.md instructionsIntermediate reasoning
    Task list (TodoWrite)File contents read in session
    Files on diskTool call history
    Git stateVerbally stated preferences
    Memory filesMulti-step conversation context
  4. Compact with an intent-carrying summary prompt, then restore.

    • Do not compact to "clean up" during active multi-file implementation
    • Pass forward intent, e.g. /compact -- now implementing auth middleware per plan
    • After compaction, re-read the task list or plan file to restore intent

Output

  • A compaction decision (do it now / wait until the next boundary) with the reason
  • A pre-compaction save of any non-reconstructible state (plan file, commit/stash, noted paths)
  • A summary prompt that carries intent into the cleared context

Token Awareness

  • Each loaded skill adds 1-5K tokens to context; load skills on demand, not at session start
  • CLAUDE.md / AGENTS.md are always loaded -- keep them lean
  • Duplicate instructions (root config plus plugin skill) are the most common waste

Verification

  • The chosen action matches the transition table -- no compaction during active multi-file implementation
  • Everything in the Lost column that is still needed was persisted (file, commit/stash, or next prompt) before compacting
  • The compact prompt carries forward intent rather than clearing blindly
  • After compaction, the task list or plan file was re-read to restore intent

Failure Modes

  • Mid-task compaction — compacting during active multi-file work and losing paths, variable names, and partial state that must then be rebuilt.
  • Compacting before saving — clearing context while the plan, WIP code, or key paths live only in conversation and not on disk or in tasks.
  • Blind compaction — using /compact with no intent summary, so the cleared session has no direction and re-derives the goal.
  • Skipping the restore step — not re-reading the task list or plan after compaction, then drifting from the original intent.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 468kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall