auto-dream

Background memory consolidation cycle. Scans memory files, finds stale, duplicate, and conflicting entries, consolidates them, synthesizes cross-session insights, builds an injection-ready payload for the next session start, and writes a dated dream report. ## When to invoke - User says "run dream", "consolidate memories", "clean up memories", "memory maintenance", "deduplicate memories" - Cron job at 2 AM nightly via wrapper script: `scripts/auto-dream-cron.sh --execute` - Manual trigger for testing: `./scripts/auto-dream-cron.sh` (dry-run by default) ## Instructions When invoked interactively (not via cron), read `skills/meta/auto-dream/dream-prompt.md` and execute its phases directly. The prompt is self-contained -- it describes the full cycle including safety constraints, file paths, and output formats. For cron invocation: the dream prompt is passed directly to `claude -p` and runs as a standalone headless session with no CLAUDE.md, no hooks, no project context. All instructions are embedded in the prompt. ## Phases 1. **SCAN** — Read all memory files and the recent git log. Write the scan document to `~/.claude/state/dream-scan-{date}.md`. 2. **ANALYZE** — Identify stale, duplicate, conflicting memories and cross-session patterns. Write analysis to `~/.claude/state/dream-analysis-{date}.md`. 3. **CONSOLIDATE** — Apply consolidation actions (max 5 changes). Archive stale/merged files, update MEMORY.md atomically. 4. **SYNTHESIZE** — Create insight memories from cr...