alex/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: replace megamemory with markdown-based memory system

Browse Source 
Remove the megamemory MCP knowledge graph and replace with plain
markdown files in .memory/ for tracking plans, research, knowledge,
and implementation state. This enables collaboration across people
and agentic coding tools (Claude Code, Copilot, Cursor, etc.).

Changes:
- Remove megamemory MCP from opencode.jsonc
- Delete tool/megamemory.ts and .megamemory/ database
- Rewrite all 25 config files to use .memory/ markdown files
- Add cross-tool instruction file awareness (AGENTS.md, CLAUDE.md,
  copilot-instructions.md, .cursorrules)
- Update save-memory, bootstrap-memory, status commands for md workflow
- Update all agent files, skills, and commands consistently
This commit is contained in:
alex
2026-03-08 18:43:46 +00:00
parent 2acdb86e3d
commit 204bbb4c84
27 changed files with 289 additions and 365 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
.config/opencode/commands/sme.md
View File

@@ -1,18 +1,18 @@
---
description: Invoke the SME (Subject Matter Expert) agent for deep domain consultation — guidance is cached in megamemory
description: Invoke the SME (Subject Matter Expert) agent for deep domain consultation — guidance is cached in .memory/decisions.md
---
You are the lead agent. The user has invoked `/sme` to consult a domain expert.
## Steps
1. Check megamemory for existing SME guidance on the requested domain (`megamemory:understand` with the domain as query). If found, return the cached guidance immediately with its concept ID.
1. Check `.memory/decisions.md` for existing SME guidance on the requested domain. If found, return the cached guidance immediately with its section heading.
2. If not cached, delegate to the `sme` agent with:
- The user's specific question
- Relevant context (project stack, constraints, current approach)
- Any relevant file paths or code snippets
3. Once SME responds, the guidance will be cached in megamemory automatically. Present the guidance to the user.
3. Once SME responds, record or update the guidance in `.memory/decisions.md`. Present the guidance to the user.
4. Link the SME guidance concept to any active plan concept in megamemory.
4. Add cross-references between the SME guidance section and any active plan file in `.memory/plans/`.