Skill: /wrap-up
The /wrap-up skill: the end-of-session handoff that writes a structured record of where work stopped and queues the slow follow-up for the next session.
The end-of-session handoff. When a session ends, this skill writes a structured handoff note into the archive, surfaces anything from the session worth capturing into long-term memory or notes, and queues the slower follow-up steps for the next session to pick up. An optional full mode runs those follow-up steps immediately instead of deferring them.
When it runs
- The session is ending ("wrap up", "I'm done", "let's stop here", "call it a day")
- Always at session end; even short sessions benefit from a record that can be searched later
What it does
- Composes the handoff: the state of work on GitHub, what was completed, what's in progress, and what comes next
- Writes it to the archive's handoffs folder, one dated note per project per day
- Surfaces memory candidates from the session's events
- Leaves a marker the next session detects, so the slow steps (sanity checks, commits, pushes) happen without blocking the session that's closing
Side effects
- Writes to the archive: the handoffs folder, and occasionally the inbox for project-outline updates
- Declares itself archive-mutating, so only one such operation runs at a time across parallel sessions
Related
- wrap-up-finalize: the follow-up sibling that runs the deferred steps
The full executable definition lives in the executive; this page is the reader's reference.