メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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.
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.
| name | memory-loop |
| description | 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. |
| license | MIT OR Apache-2.0 |
| metadata | {"aionforge-version":"0.4.1"} |
Requires an enabled Aionforge Memory MCP server.
Use this skill to make memory part of the task loop, not a final afterthought.
memory-recall. Search broadly enough to find prior decisions, preferences, blockers, release state, and failed attempts. Also recall open work with work_query / work_tree so you continue the backlog instead of re-deriving it. On every read path — search, read_memory, session_manifest, work_query — assert the teams you belong to (e.g. teams: ["aionforge-memory-team"]); read authorization is per-call, so team memory and team work items are out of scope unless you assert the team on that call. A by-id read_memory of a team memory needs that team asserted in the same call (parity with search) — it never auto-widens.work_create a work item (see the work-tracking skill); work_advance its status as it progresses. Tasks are work items, not memory episodes — and there is no "note" to store directly.work_query it. When the handoff is directed at a specific agent or teammate — not just left for whoever comes next — also message_send them a brief so they actually receive it (see the agent-messaging skill): the capture and work items make it durable, the message delivers it.consolidation_status; run consolidate only when the approval policy permits mutating derived memory.