Menu
Use during long tasks when evidence, state, and next actions must survive context compaction. Handles compaction judgment and handoff records only; no automatic hook behavior.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | compact-handoff |
| description | Use during long tasks when evidence, state, and next actions must survive context compaction. Handles compaction judgment and handoff records only; no automatic hook behavior. |
| compatibility | ["Python 3.11+ standard library"] |
compact-handoff preserves task continuity before or after context compaction. It does not trigger automatic compaction, add hooks, or create background summaries. It only defines the quality bar for a handoff that a human or future agent can safely resume.
Write a short handoff with these fields, then validate it with
scripts/compact_handoff.py <handoff-file> --json. If validation returns
status=fail, fix the handoff before compacting.
[compact-handoff]
- objective: <current objective>
- completed: <completed work>
- in-progress: <current item>
- next-step: <one next action>
- files-changed: <absolute paths>
- tests-run: <commands and results>
- forbidden-surface: <paths or actions not to touch>
- rollback: <nearest rollback path>
objective, in-progress, and next-step first.files-changed and compare it with the handoff.~/.claude/settings.json,
~/.codex/hooks.json, ~/.codex/config.toml, or ~/.agents/skills/ need a
concrete rollback path.tests-run: not run or pending produces a warning. That warning does not
block compaction, but it blocks completion claims./compact automatically.Update the per-session intent ledger for every user input and provide current intent as semantic context consumed by gates, skill-evolution, and jailbreak-detector. Keep intent summaries without storing raw prompts.
Use when the user asks about skill upgrades, update recommendations, or an evolution backlog; analyze io-trace and conduct_feedback to produce report-only evolution candidates. No automatic edits.
Use when an implementation plan already exists. Execute it in a separate session with review checkpoints.
Use when implementing a known feature, bug fix, or refactor with a resolved behavior contract. Requires a failing test before production code; use discovery first when the target or premise is unknown.
Use at the start of every coding or development conversation. Defines how to find and invoke coding-convention family skills. Requires relevant skills before any response, including clarification questions.
Runs after session-intent-analyzer and jailbreak-detector/downstream gate as their consumer. Decomposes the request and routes output, verification, lifecycle, and boundary skills without owning intake, raw intent inference, or tool permission.