Memory Merger

1---2name: memory-merger3description: 'Merges mature lessons from a domain memory file into its instruction file. Syntax: `/memory-merger >domain [scope]` where scope is `global` (default), `user`, `workspace`, or `ws`.'4---5 6# Memory Merger7 8You consolidate mature learnings from a domain's memory file into its instruction file, ensuring knowledge preservation with minimal redundancy.9 10**Use the todo list** to track your progress through the process steps and keep the user informed.11 12## Scopes13 14Memory instructions can be stored in two scopes:15 16- **Global** (`global` or `user`) - Stored in `<global-prompts>` (`vscode-userdata:/User/prompts/`) and apply to all VS Code projects17- **Workspace** (`workspace` or `ws`) - Stored in `<workspace-instructions>` (`<workspace-root>/.github/instructions/`) and apply only to the current project18 19Default scope is **global**.20 21Throughout this prompt, `<global-prompts>` and `<workspace-instructions>` refer to these directories.22 23## Syntax24 25```26/memory-merger >domain-name [scope]27```28 29- `>domain-name` - Required. The domain to merge (e.g., `>clojure`, `>git-workflow`, `>prompt-engineering`)30- `[scope]` - Optional. One of: `global`, `user` (both mean global), `workspace`, or `ws`. Defaults to `global`31 32**Examples:**33- `/memory-merger >prompt-engineering` - merges global prompt engineering memories34- `/memory-merger >clojure workspace` - merges workspace clojure memories35- `/memory-merger >git-workflow ws` - merges workspace git-workflow memories36 37## Process38 39### 1. Parse Input and Read Files40 41- **Extract** domain and scope from user input42- **Determine** file paths:43  - Global: `<global-prompts>/{domain}-memory.instructions.md` → `<global-prompts>/{domain}.instructions.md`44  - Workspace: `<workspace-instructions>/{domain}-memory.instructions.md` → `<workspace-instructions>/{domain}.instructions.md`45- The user can have mistyped the domain, if you don't find the memory file, glob the directory and determine if there may be a match there. Ask the user for input if in doubt.46- **Read** both files (memory file must exist; instruction file may not)47 48### 2. Analyze and Propose49 50Review all memory sections and present them for merger consideration:51 52```53## Proposed Memories for Merger54 55### Memory: [Headline]56**Content:** [Key points]57**Location:** [Where it fits in instructions]58 59[More memories]...60```61 62Say: "Please review these memories. Approve all with 'go' or specify which to skip."63 64**STOP and wait for user input.**65 66### 3. Define Quality Bar67 68Establish 10/10 criteria for what constitutes awesome merged resulting instructions:691. **Zero knowledge loss** - Every detail, example, and nuance preserved702. **Minimal redundancy** - Overlapping guidance consolidated713. **Maximum scannability** - Clear hierarchy, parallel structure, strategic bold, logical grouping72 73### 4. Merge and Iterate74 75Develop the final merged instructions **without updating files yet**:76 771. Draft the merged instructions incorporating approved memories782. Evaluate against quality bar793. Refine structure, wording, organization804. Repeat until the merged instructions meet 10/10 criteria81 82### 5. Update Files83 84Once the final merged instructions meet 10/10 criteria:85 86- **Create or update** the instruction file with the final merged content87  - Include proper frontmatter if creating new file88  - **Merge `applyTo` patterns** from both memory and instruction files if both exist, ensuring comprehensive coverage without duplication89- **Remove** merged sections from the memory file90 91## Example92 93```94User: "/memory-merger >clojure"95 96Agent:971. Reads clojure-memory.instructions.md and clojure.instructions.md982. Proposes 3 memories for merger993. [STOPS]100 101User: "go"102 103Agent:1044. Defines quality bar for 10/101055. Merges new instructions candidate, iterates to 10/101066. Updates clojure.instructions.md1077. Cleans clojure-memory.instructions.md108```