docs: memory capture after the final review

This commit is contained in:
bchanot committed 2026-11-04 14:05:06 +01:00
1 parent c81a7a2132
commit a4d29ea9f2
6 files changed
+11 -9

No files matched your search

+2 -1
View File
@@ -104,7 +104,8 @@ AskUserQuestion:
uncommitted for a later run.
- `edit <n>` → re-dispatch `commit-changer` with `MODE: propose` and the
user's correction for step N folded into the prompt (plus the "Captured
this session" block, as in STEP 1), so all grouping /
this session" block: reuse the same captured block from STEP 1, do not
call the tool again), so all grouping /
message judgment stays on the dispatched propose mode (`model="opus"`,
BDR-077 — never redrawn inline on the session model); show the redrawn
plan and re-ask.
+4 -3
View File
@@ -229,9 +229,10 @@ Hotfixes are often trivial (typo, config, import) — skip by default. But if th
- Bug that cost real time to locate despite being "superficial" → propose `BLK-XXX` in `.claude/memory/blockers.md` (status: resolved).
Default behaviour: `CAPITALIZE: hotfix trivial, skip` (no prompt, no output).
Exception: when memory_pending (per /capitalize STEP 1 "Captured first")
returns a `NEW` failure of the current session not marked `(sub-agent)`,
propose that one blocker draft through the same gate.
Exception: call memory_pending first (per /capitalize STEP 1 "Captured
first"); tool unavailable → the default behaviour above. When it returns a
NEW failure of the current session not marked (sub-agent), propose one
blocker draft per such failure through the same gate.
Ask the user only when there is an actual candidate to propose.
Always append a 1-line journal entry (even trivial hotfix — journal is timeline, not signal) and any approved BLK/LRN per `lib/capitalize-commit.md` § WRITE.