How do I install the Memory Governance skill?

Run npx skillmds@latest add manu-arrieta/memory-governance in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Memory Governance safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Memory Governance?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Memory Governance free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Memory Governance?

Manu-Arrieta (@manu-arrieta) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Memory Governance by manu-arrieta — Agent Skill

Name: Memory Governance
Author: Manu-Arrieta

Memory Governance

ICM memory versioning, bundle export/import, sync across workspaces, and rollback flows. Use when running /export-memory-bundle, /import-memory-bundle, /sync-workspace-memory, /rollback-workspace-memory, or when troubleshooting ICM state.

Manu-Arrieta e379693 3.7 KB Updated Sep 17, 2026

File contents

Memory Governance — Versioned ICM Operations

AOI uses governed memory versioning for workspaces registered in .specify/memory/versions/active.json. This skill describes the lifecycle of memory versions, bundles, sync, and rollback.

Version Architecture

.specify/memory/versions/
├── active.json                    # Canonical active version pointer
├── manifests/
│   └── {version-id}.json          # Immutable version manifest
├── bundles/
│   └── {version-id}.json.gz       # Exported portable bundles
└── templates/
    ├── memory-version.template.json
    ├── memory-bundle.template.json
    └── dynamic-constitution.template.md

.exportsmemories/ is where portable bundles land for cross-workspace transfer.

Core Scripts

All scripts live in scripts/memory-sync/:

Script	Purpose
`resolve-active-version.mjs`	Read active version for workspace
`prepare-version-manifest.mjs`	Create a new version manifest
`activate-version.mjs`	Set a version as active
`export-memory-bundle.mjs`	Export active version to portable bundle
`import-memory-bundle.mjs`	Import a bundle as a candidate version
`rollback-version.mjs`	Restore previous version
`bundle-contract.test.mjs`	Validate bundle schema
`bundle-lifecycle.test.mjs`	Validate full lifecycle

Bundle Lifecycle

Export (`/export-memory-bundle`)

Resolve active version: node scripts/memory-sync/resolve-active-version.mjs "$WORKSPACE"
Ask Owner for scope: full or topic-subset
Run node scripts/memory-sync/export-memory-bundle.mjs with version ID + scope
Bundle lands in .exportsmemories/{workspace}-{versionId}.json.gz
Store provenance in ICM

Import (`/import-memory-bundle` or `/sync-workspace-memory`)

Detect source (bundle file for import, workspace for sync)
Validate schema: node scripts/memory-sync/bundle-contract.test.mjs
Create candidate version via import-memory-bundle.mjs
Gate: Candidate version is NOT active yet — Owner must approve
Owner activates via /sync-workspace-memory confirmation
Dynamic constitution is updated from snapshot

Rollback (`/rollback-workspace-memory`)

Resolve active version + confirm previousVersionId
Safety check: validate previous version integrity
Run node scripts/memory-sync/rollback-version.mjs "$WORKSPACE" "$targetVersionId"
Must provide reason for rollback
Active pointer is updated atomically

Critical Constraints

Manifests under .specify/memory/versions/manifests/ are immutable — never edit them
active.json is the single source of truth for which version is active
Dynamic constitution snapshots MUST match the manifest they belong to
Rollback targets ONLY the registered previousVersionId — not arbitrary versions
Sync/import flows MUST declare sourceWorkspace + sourceVersionId

ICM Topics for Memory Governance

Always store operations under:

{WORKSPACE}-context for version activation changes
{WORKSPACE}-architecture for memoir graph updates after sync
sdd-{WORKSPACE}-memory-ops for operational logs of bundle/sync/rollback

---name: memory-governancedescription: ICM memory versioning, bundle export/import, sync across workspaces, and rollback flows. Use when running /export-memory-bundle, /import-memory-bundle, /sync-workspace-memory, /rollback-workspace-memory, or when troubleshooting ICM state.---# Memory Governance — Versioned ICM OperationsAOI uses governed memory versioning for workspaces registered in `.specify/memory/versions/active.json`. This skill describes the lifecycle of memory versions, bundles, sync, and rollback.## Version Architecture```.specify/memory/versions/├── active.json # Canonical active version pointer├── manifests/│ └── {version-id}.json # Immutable version manifest├── bundles/│ └── {version-id}.json.gz # Exported portable bundles└── templates/ ├── memory-version.template.json ├── memory-bundle.template.json └── dynamic-constitution.template.md````.exportsmemories/` is where portable bundles land for cross-workspace transfer.## Core ScriptsAll scripts live in `scripts/memory-sync/`:| Script | Purpose || ------------------------------ | ---------------------------------------- || `resolve-active-version.mjs` | Read active version for workspace || `prepare-version-manifest.mjs` | Create a new version manifest || `activate-version.mjs` | Set a version as active || `export-memory-bundle.mjs` | Export active version to portable bundle || `import-memory-bundle.mjs` | Import a bundle as a candidate version || `rollback-version.mjs` | Restore previous version || `bundle-contract.test.mjs` | Validate bundle schema || `bundle-lifecycle.test.mjs` | Validate full lifecycle |## Bundle Lifecycle### Export (`/export-memory-bundle`)1. Resolve active version: `node scripts/memory-sync/resolve-active-version.mjs "$WORKSPACE"`2. Ask Owner for scope: `full` or `topic-subset`3. Run `node scripts/memory-sync/export-memory-bundle.mjs` with version ID + scope4. Bundle lands in `.exportsmemories/{workspace}-{versionId}.json.gz`5. Store provenance in ICM### Import (`/import-memory-bundle` or `/sync-workspace-memory`)1. Detect source (bundle file for import, workspace for sync)2. Validate schema: `node scripts/memory-sync/bundle-contract.test.mjs`3. Create candidate version via `import-memory-bundle.mjs`4. **Gate**: Candidate version is NOT active yet — Owner must approve5. Owner activates via `/sync-workspace-memory` confirmation6. Dynamic constitution is updated from snapshot### Rollback (`/rollback-workspace-memory`)1. Resolve active version + confirm `previousVersionId`2. **Safety check**: validate previous version integrity3. Run `node scripts/memory-sync/rollback-version.mjs "$WORKSPACE" "$targetVersionId"`4. Must provide `reason` for rollback5. Active pointer is updated atomically## Critical Constraints- Manifests under `.specify/memory/versions/manifests/` are **immutable** — never edit them- `active.json` is the **single source of truth** for which version is active- Dynamic constitution snapshots MUST match the manifest they belong to- Rollback targets ONLY the registered `previousVersionId` — not arbitrary versions- Sync/import flows MUST declare `sourceWorkspace` + `sourceVersionId`## ICM Topics for Memory GovernanceAlways store operations under:- `{WORKSPACE}-context` for version activation changes- `{WORKSPACE}-architecture` for memoir graph updates after sync- `sdd-{WORKSPACE}-memory-ops` for operational logs of bundle/sync/rollback

Frequently asked questions