dream-summary-memorylisted

# dream-summary-memory Once a day (or on demand), the project "dreams": it replays what just happened — which findings reviewers raised, which mistakes engineers repeated across fix cycles, which CI checks kept failing, where parallel slices kept colliding — and consolidates the *patterns* into memory so the next dispatch starts smarter. It reads GitHub history (closed issues **and** closed PRs), not the runtime telemetry signals. Its only output is curated, additive overlay rules plus an audit log. It runs in the consuming project. It **never** edits the baseline pattern skills shipped by this plugin, and it **never** sends anything upstream. ## When to activate Activate this skill whenever: - The user types `/dream-summary-memory`, "dream the memory", or "summarize recent issues into memory". - A scheduled routine (`/schedule`) or `/loop /dream-summary-memory` fires it unattended. It is **autonomous**: it writes overlays without asking for per-edit approval (so it works when scheduled). It always reports what it wrote, and the `dream-log.md` is the audit trail. ## Workflow ### 1. Resolve and auto-create the memory root ```bash MAIN_ROOT="$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")" MEMORY_ROOT="$MAIN_ROOT/.claude/memory" mkdir -p "$MEMORY_ROOT/patterns" ``` Memory is always-on (see `memory-convention`); never gate on the directory pre-existing. ### 2. Determine the cutoff There is **no fixed time window**. The cutoff is the timestamp of