end

/end — Close Session

Capture the session and leave state ready for the next one: a session log, state updates, a decision-log append, memory proposals, and a git safety check.

Invocation: user-only (disable-model-invocation: true) — session close is timed by you, and the flag keeps this skill out of ambient context.

Configuration

Read the optional workspace.yaml at the project root. Below, <state_dir> and <sessions_dir> are its resolved values; defaults are state/ and sessions/. Full reference: docs/state-model.md, including the Last Updated chain protocol and the decision-log schema used in steps 3–4.

Instructions

1. Auto-extract session summary. Scan the full conversation and extract:

   • Topics covered — what was worked on
   • Decisions made — anything concluded or chosen, with rationale
   • Rejected alternatives — for each meaningful decision, what else was considered and why it lost. If a bug was fixed, note the wrong theory tried first. If an approach changed mid-session, capture the pivot. This is the failed-hypothesis record that keeps a future session from repeating the same wrong starting point.
   • State changes — priorities that shifted, threads that opened or closed
   • Open threads — unfinished items or things waiting on someone
   • Next actions — what needs to happen next session

   Present the summary for quick confirmation before writing.

2. Write session log. Append to <sessions_dir>/{TODAY}.md:

   ## Session: {TIME}
   
   ### Topics
   - {topic}
   
   ### Decisions
   - {decision}
   
   ### Open Threads
   - {thread}
   
   ### Next Actions
   - {action}
   

3. Update state files:

   • Always update current.md: add new threads, remove completed items, refresh timestamps on touched items.
   • Roll the Last Updated line through current-log.md (chain protocol). Keep exactly one **Last Updated:** line at the top of current.md, the newest. Never stack extra lines and never build a single-line "previous-entry" chain — that breaks the Read tool, breaks grep, and splices parallel-session merges into single-line conflicts. Instead:
     1. Read the existing **Last Updated:** line from current.md.
     2. Prepend it as its own line at the top of <state_dir>/current-log.md, directly under the file header, newest first. Create the file with a # current.md update log header if it does not exist.
     3. Replace the **Last Updated:** line in current.md with today's entry.