memory

# Memory

## Purpose

Centralized knowledge management for the skill ecosystem. Captures learnings from development sessions and routes them to the appropriate skill's MEMORY.md file based on knowledge type.

## Quick Reference

- **Capture**: `/memory capture "learned X"` - Route learning to appropriate skill
- **Review**: `/memory review [skill]` - Show accumulated knowledge
- **Consolidate**: `/memory consolidate` - Deduplicate and organize

## Commands

| Command | Purpose | When to Use |
|---------|---------|-------------|
| `/memory capture "..."` | Capture a learning | During/after development when something is learned |
| `/memory review` | Review all learnings | To refresh knowledge before starting work |
| `/memory review <skill>` | Review skill-specific learnings | Before using a specific skill |
| `/memory consolidate` | Clean up and organize | Periodically, or when memory feels cluttered |

---

## Memory Scopes

Knowledge is routed based on its type:

### Sub-Skill Memory (HOW knowledge)

Domain-specific knowledge about how to do things.

| Skill | Content Types |
|-------|---------------|
| `bugfix` | Debugging patterns, root cause analysis techniques |
| `tdd` | Test patterns, TDD workflow refinements |
| `arch` | Architecture decisions, layer boundary learnings |
| `code` | Code style patterns, language idioms |
| `debugger` | Production debugging, log analysis techniques |

### Orchestrator Memory (WHEN/ORDER knowledge)

Workflow knowledge about when and in what order to do things.

| Skill | Content Types |
|-------|---------------|
| `developer` | Development workflow orchestration |
| `task` | Task management and prioritization |
| `workflow` | Multi-skill coordination patterns |

---

## /memory capture

Capture a learning and route it to the appropriate skill's MEMORY.md.

### Usage

```
/memory capture "Always run tests before commit"
```

### Routing Logic

The skill analyzes your learning to determine where it belongs:

```
Is this about HO