wrap-session
Wrap Session
Execute this checklist decisively, in order. Do the work - don't ask permission for each step. Only pause to ask if something is genuinely ambiguous (e.g., unsure whether a temp script is still needed).
1. Memory
Review the full session for durable facts not yet saved to memory:
- Project facts - fps, resolution, colorspace, drive layout, folder conventions, naming schemes, tool versions, decisions made
- Feedback and corrections - anything the user corrected you on, preferences they stated, approaches they rejected
- Gotchas discovered - API quirks, version incompatibilities, workarounds that took effort to find
Write or update the relevant memory files and keep the memory index current.
Explicit check: Does the active job have its loader skill (project-<job>) and is the canonical brief ...\sandbox\AGENT\PROJECT.md current with what happened this session (decisions ledger, shot ledger, open obligations, hard rules)? If not, update them now. Job facts live THERE, not in a project_<job>.md memory file - memory keeps only a one-line pointer. If the JOB itself is finishing, run /project-wrap (project-lifecycle skill) before this wrap.