30 lines
1.5 KiB
Markdown
30 lines
1.5 KiB
Markdown
|
## 1. Install Plugin
|
||
|
|
|
||
|
|
- [x] 1.1 Run `/plugin marketplace add zilliztech/memsearch` in a Claude Code session
|
||
|
|
- [x] 1.2 Run `/plugin install memsearch` to activate the plugin
|
||
|
|
- [x] 1.3 Confirm the plugin is listed as active (no error messages)
|
||
|
|
|
||
|
|
## 2. Audit and Configure
|
||
|
|
|
||
|
|
- [x] 2.1 Run `memsearch config list` and record the actual defaults (especially `memory_dir` and `milvus_db` paths)
|
||
|
|
- [x] 2.2 If `memory_dir` is project-local, set `memory_dir = "~/.memsearch/memory/"` in `~/.memsearch/config.toml`
|
||
|
|
- [x] 2.3 Re-run `memsearch config list` to confirm `memory_dir` resolves to a global path
|
||
|
|
|
||
|
|
## 3. Verify Stop Hook
|
||
|
|
|
||
|
|
- [x] 3.1 Check `~/.claude/settings.json` (or plugin config) to confirm the memsearch Stop hook is registered
|
||
|
|
- [x] 3.2 Run a short test session (a few turns) and exit
|
||
|
|
- [x] 3.3 Confirm `~/.memsearch/memory/YYYY-MM-DD.md` exists with content from the test session
|
||
|
|
|
||
|
|
## 4. Audit Built-in Guidance
|
||
|
|
|
||
|
|
- [x] 4.1 Review what memsearch adds to Claude's context (system prompt / tool definitions)
|
||
|
|
- [x] 4.2 Run a test query: `memsearch search "what were we working on in the test session?"`
|
||
|
|
- [x] 4.3 Assess whether built-in guidance handles cross-project episodic recall without conflicting with `memory-vault`/`memory-project`
|
||
|
|
- [x] 4.4 If routing gaps are found, author a minimal `memory-search` skill; otherwise skip
|
||
|
|
|
||
|
|
## 5. Mark Complete
|
||
|
|
|
||
|
|
- [x] 5.1 Update `docs/memory-system/04-build-plan.md` — mark Step 4 complete
|
||
|
|
- [x] 5.2 Update `CLAUDE.md` — add memsearch to Implemented Components, update design paragraph
|