メニュー
Inspect, consolidate, audit, forget, or restore Aionforge Memory. Use when the user asks about memory health, backlog, provenance, stale records, corrections, deletion, restoration, or why a memory was recalled.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | memory-maintenance |
| description | Inspect, consolidate, audit, forget, or restore Aionforge Memory. Use when the user asks about memory health, backlog, provenance, stale records, corrections, deletion, restoration, or why a memory was recalled. |
| license | MIT OR Apache-2.0 |
| metadata | {"aionforge-version":"0.4.1"} |
Requires an enabled Aionforge Memory MCP server.
Use this skill when the task is about the memory system itself.
server_status if connection state is unknown.consolidation_status to inspect backlog or failed derived work.consolidate only when the user/project policy permits mutating derived memory.audit_history to explain provenance, capture receipts, supersession hints, lifecycle changes, and rejection reasons.forget or unforget only when the user explicitly names the target memory id or asks for a specific lifecycle change.work-tracking skill (work_advance to retire one to done/dropped), not forget. work_advance is itself audited, so audit_history still explains a work item's transitions.ERR_NOT_FOUND as absent or unauthorized; do not infer hidden memory existence.Send, poll, wait for, and acknowledge durable addressed agent-to-agent messages in Aionforge Memory (message_send, message_poll, message_wait, message_ack) and subscribe to room resources. Use to hand a brief to another agent, page a teammate, wait for a reply, coordinate a multi-agent workflow, or drain an inbox — distinct from recall and work tracking.
One-time setup that lays a foundational Aionforge Memory substrate for a fresh project — resolve identity, seed conventions and architecture decisions as captures, stand up a work-item backlog skeleton, and verify recall. Use when a project's memory is empty or new, or when the user asks to set up, bootstrap, initialize, or seed project memory.
Capture durable Aionforge Memory records for decisions, user preferences, project facts, release outcomes, validation results, handoffs, corrections, and reusable failure patterns. Use proactively during substantial work and whenever the user asks to remember or update memory.
Use Aionforge Memory as the working substrate for a multi-step task. Trigger for implementation, debugging, review, release, planning, incidents, handoffs, or any session where prior context and durable follow-up matter.
Search Aionforge Memory before planning, answering, coding, review, debugging, release, or continuation work. Use proactively whenever prior decisions, user preferences, project facts, failures, or handoffs could change the answer.
Track tasks, blockers, TODOs, plans, and follow-ups as durable Aionforge Memory work items. Use proactively when a multi-step task, backlog, plan, or handoff appears, and whenever the user mentions tasks, status, or what is left to do. Work items are persistent and status-tracked, distinct from decaying memory episodes.