Menu
Move a specific memory entry to a durable destination. Validates against routing rules in memory/README.md.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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-promote |
| description | Move a specific memory entry to a durable destination. Validates against routing rules in memory/README.md. |
| argument-hint | <from-description> <to-destination> (e.g. 'sqlcmd quoting trick' tools/sql-server) |
You are running the /memory-promote command. The user wants to move one specific memory entry to one specific destination. Granular alternative to /memory-dream.
Read the routing rules at ~/.claude/memory/README.md first if not already in context.
Expected form: /memory-promote <from-description> <to-destination>
<from-description>: a phrase identifying the source entry. Could be a quote, a topic name, or a date+timestamp (e.g. "today's 14:30 sql-server bullet"). If unclear, ask for clarification.<to-destination>: one of:
<rule-name> → ~/.claude/memory/<rule-name>.md (top-level rule file; one rule per file, kebab-case)tools/<X> → ~/.claude/memory/tools/<X>.mddomain/<X> → ~/.claude/memory/domain/<X>.mdrepo/<rule-name>, repo/tools/<X>, repo/domain/<X> → expands to <git-root>/.claude/memory/.... Requires cwd inside a git repo.If $ARGUMENTS is empty, ask for both source and destination.
Identify the source entry: search dailies first (~/.claude/memory/daily/*.md), then global durables, then repo durables. If multiple matches, list them and ask which.
Identify the target destination from the second argument. If the destination is repo/... and cwd isn't in a git repo, abort with a clear message.
Validate against the routing rules:
Show the proposed move:
Wait for approval.
Apply:
## HH:MM — topic section from the daily file. Content now lives in the destination; keeping it in the daily is duplication.MEMORY.md index in the destination store: bump the last-updated date for the destination file. If a new file was created, also add a new descriptive index entry.~/.claude/projects/<mapped-cwd>/memory/./memory-dream instead.