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-25-report-warning-example.md
View on GitHub# Report Warning Example 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:** Add a warning-state `report` example to the README files so users can see what the command looks like when files are missing.
**Architecture:** Keep the change documentation-only. Update the contract test first, then add a short warning example block to each README next to the existing normal-output example. The example must match the current CLI wording and section order.
**Tech Stack:** Markdown docs, plain `pytest`
---
### Task 1: Add contract coverage for the warning example
**Files:**
- Modify: `tests/test_memory_capture_contract.py`
- Test: `tests/test_memory_capture_contract.py`
- [ ] **Step 1: Write the failing contract assertions**
```python
assert 'Missing supported file: SESSION-STATE.md' in readme_text
assert 'Warnings:' in readme_text
```
- [ ] **Step 2: Run test to verify it fails**
Run: `pytest tests/test_memory_capture_contract.py -v`
Expected: FAIL because the README files only contain the success example.
- [ ] **Step 3: Write minimal implementation**
Add one warning-state output example to:
- `README.md`
- `README_CN.md`
- `README_EN.md`
- [ ] **Step 4: Run test to verify it passes**
Run: `pytest tests/test_memory_capture_contract.py -v`
Expected: PASS
- [ ] **Step 5: Commit**
```bash
git add README.md README_CN.md README_EN.md tests/test_memory_capture_contract.py
git commit -m "docs: add report warning output example"
```
### Task 2: Verify the repository
**Files:**
- No new files; verify the repo state
- [ ] **Step 1: Run full verification**
Run: `pytest -q`
Expected: all tests pass.
- [ ] **Step 2: Inspect repo state**
Run: `git status --short`
Expected: only intended modifications remain.
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 |