From acb49a46c3850304acb84e0accabc8f5fb7d19c7 Mon Sep 17 00:00:00 2001 From: Viktor Barzin Date: Sun, 19 Apr 2026 13:32:48 +0000 Subject: [PATCH] =?UTF-8?q?execution.md=20=C2=A78:=20wrap-up-session=20tri?= =?UTF-8?q?gger?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit When the user says "let's wrap up" (or similar), walk a 6-step checklist: close beads, update docs, commit, push, wait for CI, persist learnings to memory. Ties together §3 (push), §7 (docs), the CLAUDE.md beads rule, and the existing memory-on-commit preference. Co-Authored-By: Claude Opus 4.7 (1M context) --- dot_claude/rules/execution.md | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/dot_claude/rules/execution.md b/dot_claude/rules/execution.md index f458606..23d5caa 100644 --- a/dot_claude/rules/execution.md +++ b/dot_claude/rules/execution.md @@ -115,3 +115,33 @@ have `docs/` directories. See also: `infra/.claude/CLAUDE.md` "Update docs with every change" for the full list of doc surfaces (includes `.claude/CLAUDE.md`, `AGENTS.md`, `.claude/reference/service-catalog.md`). + +## 8. Wrapping up a session + +Triggered by the user saying anything like "let's wrap up", "wrap up +the session", "we're done", "end of session", or similar. When you +hear this, run this checklist end-to-end (no mid-checklist gates): + +1. **Close beads tasks you touched this session.** + - Completed work → `bd close `, or add `Closes: ` / `Fixes: + ` trailer to the wrap-up commit (the post-commit hook auto-closes). + - Partial work → drop back to `open` with + `bd note "progress summary — where to pick up"`. Never leave + `in_progress` tasks stale across sessions. + - Check with `bd list --status in_progress` to confirm nothing of + yours is still flagged. +2. **Update docs** per §7 — any `infra/docs/` surfaces touched by the + session's work. Don't land the wrap-up commit with stale docs. +3. **Commit outstanding work.** Stage specific files by name (§3). + Write a commit message that explains the session's goal and result, + not a file-by-file changelog. +4. **Push to remote** per §3 — direct to master for personal repos, + PR flow for shared. +5. **Wait for CI / deployment** to finish before declaring done (§3). +6. **Persist learnings to memory.** For any non-obvious decisions, + patterns, or gotchas discovered during the session, call + `mcp__claude_memory__memory_store` with a concise summary. This is + what future sessions will recall — skip the obvious, keep the + surprising. + +Stop only for items on §2's ASK-FIRST list.