LeoYeAI/agent-master-skills / skills/agent-memory-system-guide
Agent Memory System Guide
VerifiedAn agent memory workflow guide for OpenClaw and Codex with MEMORY.md, daily notes, SESSION-STATE, working-buffer, Obsidian archiving, and optional OpenViking support.
docs/superpowers/plans/2026-03-27-memory-positioning.md
View on GitHub# Memory Positioning and Boundary Implementation Plan
> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
**Goal:** Clarify repository positioning in the documentation so users understand the local-first workflow, memory boundaries, and optional backend story.
**Architecture:** Update the README entry points and install wording only. Keep the script and template contract unchanged while making the documentation reflect stable profile, active context, and optional recall backend concepts.
**Tech Stack:** Markdown, repository contract tests, pytest
---
### Task 1: Document the intended product boundary
**Files:**
- Create: `docs/superpowers/specs/2026-03-27-memory-positioning-design.md`
- Modify: `README.md`
- Modify: `README_EN.md`
- Modify: `README_CN.md`
- Modify: `INSTALL.md`
- Test: `tests/test_readme_openviking_optional.py`
- Test: `tests/test_install_contract.py`
- [ ] **Step 1: Update README openings**
Add wording that this repository is a local-first Agent memory workflow rather than a hosted memory platform, while preserving the existing OpenViking-optional contract language.
- [ ] **Step 2: Add explicit boundary sections**
Document the roles of `SESSION-STATE.md`, `working-buffer.md`, `MEMORY.md`, `memory/`, and deeper archive or semantic recall layers.
- [ ] **Step 3: Add stable profile and project scope guidance**
Explain that `MEMORY.md` should bias toward durable profile information and that project references are optional conventions when one workspace spans multiple efforts.
- [ ] **Step 4: Update install wording**
Keep the OpenViking phrase required by tests, but broaden the wording to "optional enhancement/backend" rather than implying a single integration path.
### Task 2: Verify documentation contracts
**Files:**
- Modify: none
- Test: `tests/test_readme_openviking_optional.py`
- Test: `tests/test_install_contract.py`
- Test: full `tests/`
- [ ] **Step 1: Run targeted documentation contract tests**
Run: `pytest tests/test_readme_openviking_optional.py tests/test_install_contract.py -q`
Expected: PASS
- [ ] **Step 2: Run full regression suite**
Run: `pytest -q`
Expected: PASS
- [ ] **Step 3: Inspect diff**
Run: `git diff -- README.md README_EN.md README_CN.md INSTALL.md docs/superpowers/specs/2026-03-27-memory-positioning-design.md docs/superpowers/plans/2026-03-27-memory-positioning.md`
Expected: Documentation-only changes that align with the local-first positioning and optional backend wording.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |