signofflisted

# /signoff — structured end-of-session ritual Run this when the user intentionally wraps a session. Four core steps, none optional. Each step writes to durable state so the next session — yours or another agent's — can pick up cold. The core insight: sessions don't fail at the start, they fail at the *end*. An unstructured ending means the next cold start re-derives everything from scratch. This skill makes the ending mechanical so the next beginning is instant. ## When to invoke The user types any of: - `/signoff` - `wrap up` - `update progress` - `end session` - `i'm stepping away` - `let's wrap` - `before I head out` Also invoke when: - A meaningful build just completed (milestone hit, deploy shipped) and the conversation is naturally winding down - The user message contains both "thanks" + a goal-state phrase ("that's it for now", "looks good") ## DO NOT invoke when - Mid-build with open todos - The user asked an exploratory question and is still iterating - The session is fewer than ~5 turns old (nothing to capture yet) Auto-signing-off when the user didn't actually ask is worse than not having the skill. Mid-build "let me check something" is not a signal. The trigger phrases are explicit for a reason. --- ## The four steps (run in order) ### Step 1 — Snapshot what this session touched Build a session changelog. Sources: - **Edit / Write / NotebookEdit calls** this session — your own tool-call history is the ground truth - **Shell commands with side effect