memory

Saves and loads agent session state as Markdown files in a project progress directory.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill memory-archaonhw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/memory
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill memory-archaonhw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agent sessions lose context between runs, forcing users to re-explain prior work. This Skill provides a persistent file-based backend so agents can save their state at session end and reload it at the next session start. ## Core Features & Use Cases - Save Operation: Writes a compiled agent state block (Wrapped, Context, Plan, Next, Learned, Spec Sync fields) to progress/[agent_id].md at the project root. - Load Operation: Reads back the stored state file for a given agent, returning nothing when no prior state exists so callers can handle fresh starts. - Use Case: A developer wraps up a work session with the saga agent; the wrap tool calls this Skill to persist the session state, and the next day's start tool reloads it to resume exactly where work stopped. ## Quick Start Ask the agent to save its current session state to the project progress folder so it can be restored at the next session start.

Frequently Asked Questions about memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist AI agent session state between runs?

Save the agent's compiled state block to a Markdown file named after the agent_id in a progress directory at the project root. On the next session, load that file back to restore context such as the plan, next steps, and learned items.

Where is the session state stored?

State is stored in a progress folder at the project root, with one Markdown file per agent (progress/[agent_id].md). It is project-scoped and machine-local, not global or synced across machines.

Should the progress folder be committed to git?

No, the progress directory should be added to .gitignore. It contains machine-local session context rather than project content, so committing it would leak local state into the shared repository.

What happens when no saved state file exists for an agent?

The load operation returns nothing when progress/[agent_id].md is missing. The calling tool, such as the start tool, is responsible for handling that case as a fresh start.

Is this state backend shared or synced across machines?

No, the backend is purely local file storage with no tokens, async operations, or network sync. State stays on the machine and project where it was written.