Menú
Triage daily logs - propose promotions to durable memory and archive of older dailies. Plan-then-apply.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices, and publish them to the repo's GitHub Project board. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
Turn the current conversation context into a PRD and publish it to the repo's GitHub Project board. Use when user wants to create a PRD from the current context.
Compact the current conversation into a handoff document for another agent to pick up.
| name | memory-dream |
| description | Triage daily logs - propose promotions to durable memory and archive of older dailies. Plan-then-apply. |
You are running the /memory-dream command. Three things happen, all gated by user approval:
daily/archive/<year>/.MEMORY.md is refreshed.Read the routing rules at ~/.claude/memory/README.md first if not already in context.
Two distinct reads — different roles:
~/.claude/memory/daily/ (excluding daily/archive/).~/.claude/memory/*.md (top-level rule files, one concept per file), tools/*.md, domain/*.md (global durables)git rev-parse --show-toplevel), also <repo>/.claude/memory/*.md, <repo>/.claude/memory/tools/*.md, <repo>/.claude/memory/domain/*.md (repo durables)Present a plan organized as four groups:
Promote → durable memory: recurring themes, durable decisions, codebase facts that benefit teammates.
<rule-name>.md (NEW top-level rule file): …"tools/sql-server.md (NEW): …"<repo>/.claude/memory/<rule-name>.md (NEW): …"README.md and check reference material to avoid dupes.Skip (not durable yet — leave in daily for context): bullets that aren't worth promoting today but might recur. They stay in their daily file. No movement.
Archive → daily/archive/<year>/: older daily files (>30 days old by default) whose contents have either been promoted or have no further signal. Archiving moves the whole daily/<YYYY-MM-DD>.md file to daily/archive/<YYYY>/<YYYY-MM-DD>.md. The hook stops injecting them, but the file is preserved on disk.
Already in durable memory (informational): daily entries that already correspond to durable bullets — no action needed.
For each approved item:
## HH:MM — topic section). Content now lives in the topic file; leaving it in the daily is duplication. Skipped (not-promoted) entries stay in the daily for pattern detection over time.mkdir -p ~/.claude/memory/daily/archive/<year>/ and mv the daily file there. Use plain mv — daily files are gitignored, no git history involvement.~/.claude/memory/MEMORY.md index: bump last-updated dates for topic files touched. Daily files are not indexed; promoted bullets land in topic files which already have their own index sections.~/.claude/projects/<mapped-cwd>/memory/ — that's Anthropic's auto-memory.