---
name: Memory
slug: memory-2
category: AI Engineering
description: Memory stores durable orchestrator lessons and stable preferences for future work. Use it when deciding whether to write, read, update, consolidate, or avoid memory versus board status, job state, session history, or project context.
github: "https://github.com/prassanna-ravishankar/repowire/tree/main/daemon-go/cli/assets/orchestrator/.agents/skills/memory"
language: Go
stars: 260
forks: 34
install: "npx degit https://github.com/prassanna-ravishankar/repowire/tree/main/daemon-go/cli/assets/orchestrator/.agents/skills/memory ~/.claude/skills/memory"
installs_to: ~/.claude/skills/memory
source_path: daemon-go/cli/assets/orchestrator/.agents/skills/memory/SKILL.md
collection_size: 17
category_size: 2631
collection_url: "https://dirskills.com/collections/prassanna-ravishankar/repowire"
added: 2026-09-02T05:20:19.576Z
last_synced: 2026-09-02T05:20:19.576Z
canonical_url: "https://dirskills.com/skills/memory-2"
---

# Memory

Memory stores durable orchestrator lessons and stable preferences for future work. Use it when deciding whether to write, read, update, consolidate, or avoid memory versus board status, job state, session history, or project context.

**Install:**

```bash
npx degit https://github.com/prassanna-ravishankar/repowire/tree/main/daemon-go/cli/assets/orchestrator/.agents/skills/memory ~/.claude/skills/memory
```

## README

# Memory

Memory is for durable operational lessons: "next time X comes up, do Y differently." It is not status, history, transcript recall, or job state.

Use Repowire memory for orchestrator lessons:

```bash
repowire memory list --scope orchestrator
repowire memory show <slug> --scope orchestrator
repowire memory search <query> --scope orchestrator
repowire memory write <slug> --scope orchestrator --body "..." --type lesson --description "..."
```

## What belongs where

- Memory: forward-applicable operating lessons and stable preferences.
- Board: owner, state, blocker, next action.
- Jobs: attempts, lifecycle state, failures, results.
- Session history/search: detailed recall and evidence.
- Project agent files: context peers in that project should always load.

Other peers do not inherit orchestrator memory implicitly. Include relevant memory context in briefs when it materially changes the work.

## Write rules

Write after an explicit durable-memory decision or a clear correction that should change future behavior. Keep each memory focused and short. If two memories overlap, consolidate. If a memory becomes stale, update it rather than adding a competing rule.

Do not save one-off events, activity counts, recent work summaries, or full histories as memory.