← ClaudeAtlas

sessionendlisted

End-of-session ritual — reflects on what happened, stores a structured session summary to the correct department Brain, updates the Master Dashboard, updates the Master Brain awareness layer, and updates local memory. Use when the user types /sessionend or says they're done for the session, wrapping up, or signing off.
cerebrocybersolutions/libro · ★ 0 · AI & Automation · score 75
Install: claude install-skill cerebrocybersolutions/libro
# Session End A closing ritual that turns each session into institutional memory. Goal: nothing gets lost between sessions, and an honest record builds over time so the system improves. --- ## BRAIN STRUCTURE — Know Before You Write ``` Master Brain (Chief of Staff): {brain_root}/mission-control/ DASHBOARD.md ← status table — update every sessionend awareness.md ← narrative layer — update every sessionend decisions/ ← ops-level, cross-dept decisions sessions/ ← master/ops sessions only Department Brains (kebab-case, lowercase `brain/` at every dept): {operator_departments} — configured in brain.config.yml at install time # Pattern: # {dept}/brain/sessions/ | decisions/ ``` Department codes: configured in `brain.config.yml` — set at install time per operator's dept roster. --- ## Step 1 — Read the Session Review the conversation — what was built, decided, or left unfinished. Run a quick git check: ```bash git -C $(pwd) log --oneline --since="8 hours ago" 2>/dev/null || true ``` --- ## Step 2 — Confirm Department Auto-detect the department from what was worked on. Ask operator with a single short line: > "Wrapping up as **[dept]** — good?" One word confirms. If they name a different dept, use that. For multi-dept sessions: "Wrapping up as **sales + ops** — good?" --- ## Step 3 — Reflect Honestly Before writing, evaluate — don't just summarize: - What was actually accomplished? (concrete outputs, not eff