memguardlisted

# MemGuard Skill — Agent SOP Router > **You have been equipped with the `memguard` MCP server (3 tools). > This SOP tells you WHEN and HOW to use them.** > > **MCP tools**: `memguard_runtime_bootstrap` | `memguard_runtime_query_memory` > | `memguard_runtime_commit_event` > > **Detailed rules** (ADR lifecycle, Task lifecycle, Trap format, Archive format, > Task lookup) are in `references/*.md` — load on demand when needed. > > **Design philosophy**: continuity > statelessness · decisions > conversation > history · active context > historical detail --- ## 0. Activation If this document is visible in the current context, MemGuard is already active. **The activation decision has already been made. Do not re-evaluate whether MemGuard should be used.** **Do NOT call `skill("memguard")`.** Proceed directly with the Bootstrap → Query → Commit workflow below. This SOP and the MCP tools are the instruction layer and the execution layer, respectively. Both are already available. --- ## 1. Quick Trigger Guide Match the user's intent to the minimum MemGuard workflow: | User asks about | Required action | | --------------- | --------------- | | Existing task or task status | `bootstrap()` + `task_lookup()` | | Architecture, design, or technology choice | `bootstrap()` + `query_memory()` | | Refactor or core module change | `bootstrap()` + `query_memory()` | | New feature or library introduction | `bootstrap()` + `query_memory()` | | Bug or error with a reusable fix | `bootstrap(