Menú
End-of-day close: the user is stepping away and won't serve as a bridge. Full collaborative triage, working-style reflection, and anticipatory framing for the next day. Invoke with /session-close.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
| name | session-close |
| description | End-of-day close: the user is stepping away and won't serve as a bridge. Full collaborative triage, working-style reflection, and anticipatory framing for the next day. Invoke with /session-close. |
Actually putting the device down. The user is leaving — going to sleep, stepping away for the evening, taking a real break. The bridge goes away. The next session starts with only what's written down plus whatever the user remembers after a real break.
This is the most thorough transition protocol. It includes everything session-rest does, plus:
Stance composition: Inherit session-rest's phase-specific composition.
For the close-specific reflection and framing, use:
interpretive-synthesis to read cross-session patterns,
diagnostic-questioning with socratic-elicitation to reflect with the
user, and relational-continuity to prepare tomorrow's starting point.
Run the full session-rest protocol: reconcile Project Orientation, interpret inside the Current bet, triage evidence and tensions, draft, and validate. Inherit its continue-or-steer boundary rather than recreating project selection here. The triage should be more thorough than a between-sessions rest — the user won't be around to fill in gaps, so the trajectory document needs to carry more weight.
In Phase 3 (triage), don't rely on the user bridging nuances. Ask about threads that would be low-variance in a session-rest — the user might remember them now, but they won't tomorrow.
In Phase 4 (draft), write for a reader who has slept since the last session. Context that feels obvious now will be cold tomorrow.
This phase captures things that don't belong in the trajectory but matter for future sessions.
Reflect on how the collaboration worked during this session. What patterns emerged in how the user and agent worked together? This is metacognition — stepping back from the work to observe the process.
Update /memories/collaborative-style.md (user memory, persists across all workspaces) with observations about:
Don't overwrite previous observations — add to them. Working style evolves over time, and earlier observations provide context for later ones.
If this session is part of a longer arc of work, note patterns that span sessions as evidence about the Current bet and its route:
These go in Evidence and Route Changes or Live Tensions. They can clarify whether the bet still advances its Experienced outcome; they do not infer a new Vision from session momentum.
Arrange the desk for tomorrow around the reconciled Project Orientation:
When the bet remains active, this framing makes its Immediate gate easy to resume. When a steering boundary is already open, carry that reached or steering-in-progress state forward instead of choosing tomorrow's project priority independently. This goes in the trajectory document and transition prompt.
For end-of-day closes, invoke the pre-read agent to produce a SESSION-BRIEFING.md. The user won't remember codebase details tomorrow — the briefing provides the orientation that the user's memory would normally supply.
Give the pre-read agent the transition prompt, SESSION-TRAJECTORY.md, its Project Orientation, and every named orientation source. Ask it to map terrain for Current bet → Immediate gate, or to map evidence relevant to an already-open steering boundary. The briefing goes in /memories/repo/SESSION-BRIEFING.md using the memory tool.
Run one more validation pass with the combined prompt.
Update /memories/active-handoffs.md (user memory) with the current repo/branch/date/status.
Write a transition prompt (≤5 lines) for the next session. Name the recorded Immediate gate verbatim, or the already-open steering boundary, rather than synthesizing a new priority. The user will be reading it with fresh but cold eyes.
This prompt is the input to the session-load skill.
/memories/repo/SESSION-TRAJECTORY.md (via memory tool)/memories/collaborative-style.md (user memory)/memories/active-handoffs.md entry/memories/repo/SESSION-BRIEFING.md (recommended for end-of-day)Basado en la clasificación ocupacional SOC
Review the conversation for threads that were started but not followed — ideas mentioned in passing, decisions deferred implicitly, tensions named but not resolved. Use when taking stock, before saving, or whenever the user wants to know what's been left on the table.
Use when drafting, updating, or reviewing a GitHub pull request title or body, including PR creation flows that need reviewer-facing prose. Follow the repo PR template when present, preserve the user's or project's voice, and route validation/session details to the right surface.
Start a new session cycle by reconciling Project Orientation, restoring repo context, and resuming the active bet or opening vision steering when selection genuinely changed.
End-of-cycle transition: interpret the session, triage dangling threads with the user, and prepare SESSION-TRAJECTORY.md for the next cycle. The user is still around and serves as a light bridge. Invoke with /session-rest.
Keeps SESSION-TRAJECTORY.md warm as work progresses and offers checkpoints at natural boundaries. Saving is not stopping.
Use when coordinating multiple live Codex threads, maintaining a coordination heartbeat, routing work across implementation threads, inspecting cross-thread ownership or gates, or keeping a coordinated effort moving through PR, review, evidence, and human-action boundaries.
