aiwfx-handoff

Generates a paste-ready compaction handoff block summarizing volatile session state for /compact.

Updated May 9, 2026
One-click install
npx skills add https://github.com/23min/aiwf --skill aiwfx-handoff-23min
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiwfx-handoff
Source: https://github.com/23min/aiwf/tree/main/internal/skills/embedded-rituals/plugins/aiwf-extensions/skills/aiwfx-handoff
Command: npx skills add https://github.com/23min/aiwf --skill aiwfx-handoff-23min

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a long AI-assisted coding session approaches context limits, composing a handoff message for /compact becomes a from-scratch task done at an unpredictable moment. This Skill removes that compose step by emitting a short, paste-ready block that carries only what git and the aiwf planning tree cannot reconstruct. ## Core Features & Use Cases - Volatile-first handoff block: Emits a six-line block carrying the live reasoning thread, session gotchas, the exact next action, and decisions taken, while pointing into the tree (aiwf show, aiwf status, aiwf history) for durable state. - Length discipline: Caps output at roughly ten lines, treating overflow as a signal that committed state is being re-summarized instead of referenced. - Flexible cadence: Fires on request anywhere in a conversation, unconditionally at milestone close, and on demand at acceptance-criteria boundaries. - Use Case: Before compacting a long session on milestone M-0007, ask for a handoff and paste the emitted block directly into /compact so the next session resumes with the rejected approaches and next action intact. ## Quick Start Ask the assistant to give you a handoff or prime the compact before running /compact, then paste the emitted block as the compact argument.

Frequently Asked Questions about aiwfx-handoff

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

FAQPage Schema
How do I preserve context when using /compact in a long coding session?

Request a handoff before compacting and paste the emitted block as the /compact argument. The block carries the volatile reasoning thread, session gotchas, and exact next action that committed state cannot reconstruct.

What should a compaction handoff message include?

Include only volatile information: the live reasoning thread, approaches tried and rejected, traps to avoid, the exact next action, and decisions made this session. Point to durable state with commands like aiwf show and aiwf status instead of re-summarizing it.

Does the handoff skill write files or modify the planning tree?

No, it is strictly read-only over the planning tree. It emits the block inline with no mutation, no commit, and no file written, since a persisted HANDOFF.md would become a stale duplicate of committed state.

Why is my handoff block too long?

Running past roughly ten lines signals the block is re-summarizing durable state that aiwf status or aiwf show already reconstructs. Replace the excess with a pointer command and keep only the volatile payload.

When should I trigger a compaction handoff?

Trigger it on request whenever context grows long, unconditionally at milestone close, and on demand at acceptance-criteria boundaries. It is not needed after every acceptance criterion since compaction is not a per-AC event.