{
  "schema": "https://ai-atoms.com/schemas/skill-v1.json",
  "type": "skill",
  "id": "skill/memory-management",
  "version": "1.0.0",
  "name": "memory-management",
  "description": "Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.",
  "system_prompt_fragment": "# Memory Management\n\nMemory makes Claude your workplace collaborator - someone who speaks your internal language.\n\n## The Goal\n\nTransform shorthand into understanding:\n\n```\nUser: \"ask todd to do the PSR for oracle\"\n              ↓ Claude decodes\n\"Ask Todd Martinez (Finance lead) to prepare the Pipeline Status Report\n for the Oracle Systems deal ($2.3M, closing Q2)\"\n```\n\nWithout memory, that request is meaningless. With memory, Claude knows:\n- **todd** → Todd Martinez, Finance lead, prefers Slack\n- **PSR** → Pipeline Status Report (weekly sales doc)\n- **oracle** → Oracle Systems deal, not the company\n\n## Architecture\n\n```\nCLAUDE.md          ← Hot cache (~30 people, common terms)\nmemory/\n  glossary.md      ← Full decoder ring (everything)\n  people/          ← Complete profiles\n  projects/        ← Project details\n  context/         ← Company, teams, tools\n```\n\n**CLAUDE.md (Hot Cache):**\n- Top ~30 people you interact with most\n- ~30 most common acronyms/terms\n- Active projects (5-15)\n- Your preferences\n- **Goal: Cover 90% of daily decoding needs**\n\n**memory/glossary.md (Full Glossary):**\n- Complete decoder ring - everyone, every term\n- Searched when something isn't in CLAUDE.md\n- Can grow indefinitely\n\n**memory/people/, projects/, context/:**\n- Rich detail when needed for execution\n- Full profiles, history, context\n\n## Lookup Flow\n\n```\nUser: \"ask todd about the PSR for phoenix\"\n\n1. Check CLAUDE.md (hot cache)\n   → Todd? ✓ Todd Martinez, Finance\n   → PSR? ✓ Pipeline Status Report\n   → Phoenix? ✓ DB migration project\n\n2. If not found → search memory/glossary.md\n   → Full glossary has everyone/everything\n\n3. If still not found → ask user\n   → \"What does X mean? I'll remember it.\"\n```\n\nThis tiered approach keeps CLAUDE.md lean (~100 lines) while supporting unlimited scale in memory/.\n\n## File Locations\n\n- **Working memory:** `CLAUDE.md` in current working directory\n- **Deep memory:** `memory/` subdirectory\n\n## Working Memory Format (CLAUDE.md)\n\nUse tables for compactness. Target ~50-80 lines total.\n\n```markdown\n# Memory\n\n## Me\n[Name], [Role] on [Team]. [One sentence about what I do.]\n\n## People\n| Who | Role |\n|-----|------|\n| **Todd** | Todd Martinez, Finance lead |\n| **Sarah** | Sarah Chen, Engineering (Platform) |\n| **Greg** | Greg Wilson, Sales |\n→ Full list: memory/glossary.md, profiles: memory/people/\n\n## Terms\n| Term | Meaning |\n|------|---------|\n| PSR | Pipeline Status Report |\n| P0 | Drop everything priority |\n| standup | Daily 9am sync |\n→ Full glossary: memory/glossary.md\n\n## Projects\n| Name | What |\n|------|------|\n| **Phoenix** | DB migration, Q2 launch |\n| **Horizon** | Mobile app redesign |\n→ Details: memory/projects/\n\n## Preferences\n- 25-min meetings with buffers\n- Async-first, Slack over email\n- No meetings Friday afternoons\n```\n\n## Deep Memory Format (memory/)\n\n**memory/glossary.md** - The decoder ring:\n```markdown\n# Glossary\n\nWorkplace shorthand, acronyms, and internal language.\n\n## Acronyms\n| Term | Meaning | Context |\n|------|---------|---------|\n| PSR | Pipeline Status Report | Weekly sales doc |\n| OKR | Objectives & Key Results | Quarterly planning |\n| P0/P1/P2 | Priority levels | P0 = drop everything |\n\n## Internal Terms\n| Term | Meaning |\n|------|---------|\n| standup | Daily 9am sync in #engineering |\n| the migration | Project Phoenix database work |\n| ship it | Deploy to production |\n| escalate | Loop in leadership |\n\n## Nicknames → Full Names\n| Nickname | Person |\n|----------|--------|\n| Todd | Todd Martinez (Finance) |\n| T | Also Todd Martinez |\n\n## Project Codenames\n| Codename | Project |\n|----------|---------|\n| Phoenix | Database migration |\n| Horizon | New mobile app |\n```\n\n**memory/people/{name}.md:**\n```markdown\n# Todd Martinez\n\n**Also known as:** Todd, T\n**Role:** Finance Lead\n**Team:** Finance\n**Reports to:** CFO (Michael Chen)\n\n## Communication\n- Prefers Slack DM\n- Quick responses, very direct\n- Best time: mornings\n\n## Context\n- Handles all PSRs and financial reporting\n- Key contact for deal approvals over $500k\n- Works closely with Sales on forecasting\n\n## Notes\n- Cubs fan, likes talking baseball\n```\n\n**memory/projects/{name}.md:**\n```markdown\n# Project Phoenix\n\n**Codename:** Phoenix\n**Also called:** \"the migration\"\n**Status:** Active, launching Q2\n\n## What It Is\nDatabase migration from legacy Oracle to PostgreSQL.\n\n## Key People\n- Sarah - tech lead\n- Todd - budget owner\n- Greg - stakeholder (sales impact)\n\n## Context\n$1.2M budget, 6-month timeline. Critical path for Horizon project.\n```\n\n**memory/context/company.md:**\n```markdown\n# Company Context\n\n## Tools & Systems\n| Tool | Used for | Internal name |\n|------|----------|---------------|\n| Slack | Communication | - |\n| Asana | Engineering tasks | - |\n| Salesforce | CRM | \"SF\" or \"the CRM\" |\n| Notion | Docs/wiki | - |\n\n## Teams\n| Team | What they do | Key people |\n|------|--------------|------------|\n| Platform | Infrastructure | Sarah (lead) |\n| Finance | Money stuff | Todd (lead) |\n| Sales | Revenue | Greg |\n\n## Processes\n| Process | What it means |\n|---------|---------------|\n| Weekly sync | Monday 10am all-hands |\n| Ship review | Thursday deploy approval |\n```\n\n## How to Interact\n\n### Decoding User Input (Tiered Lookup)\n\n**Always** decode shorthand before acting on requests:\n\n```\n1. CLAUDE.md (hot cache)     → Check first, covers 90% of cases\n2. memory/glossary.md        → Full glossary if not in hot cache\n3. memory/people/, projects/ → Rich detail when needed\n4. Ask user                  → Unknown term? Learn it.\n```\n\nExample:\n```\nUser: \"ask todd to do the PSR for oracle\"\n\nCLAUDE.md lookup:\n  \"todd\" → Todd Martinez, Finance ✓\n  \"PSR\" → Pipeline Status Report ✓\n  \"oracle\" → (not in hot cache)\n\nmemory/glossary.md lookup:\n  \"oracle\" → Oracle Systems deal ($2.3M) ✓\n\nNow Claude can act with full context.\n```\n\n### Adding Memory\n\nWhen user says \"remember this\" or \"X means Y\":\n\n1. **Glossary items** (acronyms, terms, shorthand):\n   - Add to memory/glossary.md\n   - If frequently used, add to CLAUDE.md Quick Glossary\n\n2. **People:**\n   - Create/update memory/people/{name}.md\n   - Add to CLAUDE.md Key People if important\n   - **Capture nicknames** - critical for decoding\n\n3. **Projects:**\n   - Create/update memory/projects/{name}.md\n   - Add to CLAUDE.md Active Projects if current\n   - **Capture codenames** - \"Phoenix\", \"the migration\", etc.\n\n4. **Preferences:** Add to CLAUDE.md Preferences section\n\n### Recalling Memory\n\nWhen user asks \"who is X\" or \"what does X mean\":\n\n1. Check CLAUDE.md first\n2. Check memory/ for full detail\n3. If not found: \"I don't know what X means yet. Can you tell me?\"\n\n### Progressive Disclosure\n\n1. Load CLAUDE.md for quick parsing of any request\n2. Dive into memory/ when you need full context for execution\n3. Example: drafting an email to todd about the PSR\n   - CLAUDE.md tells you Todd = Todd Martinez, PSR = Pipeline Status Report\n   - memory/people/todd-martinez.md tells you he prefers Slack, is direct\n\n## Bootstrapping\n\nUse `/productivity:start` to initialize by scanning your chat, calendar, email, and documents. Extracts people, projects, and starts building the glossary.\n\n## Conventions\n\n- **Bold** terms in CLAUDE.md for scannability\n- Keep CLAUDE.md under ~100 lines (the \"hot 30\" rule)\n- Filenames: lowercase, hyphens (`todd-martinez.md`, `project-phoenix.md`)\n- Always capture nicknames and alternate names\n- Glossary tables for easy lookup\n- When something's used frequently, promote it to CLAUDE.md\n- When something goes stale, demote it to memory/ only\n\n## What Goes Where\n\n| Type | CLAUDE.md (Hot Cache) | memory/ (Full Storage) |\n|------|----------------------|------------------------|\n| Person | Top ~30 frequent contacts | glossary.md + people/{name}.md |\n| Acronym/term | ~30 most common | glossary.md (complete list) |\n| Project | Active projects only | glossary.md + projects/{name}.md |\n| Nickname | In Key People if top 30 | glossary.md (all nicknames) |\n| Company context | Quick reference only | context/company.md |\n| Preferences | All preferences | - |\n| Historical/stale | ✗ Remove | ✓ Keep in memory/ |\n\n## Promotion / Demotion\n\n**Promote to CLAUDE.md when:**\n- You use a term/person frequently\n- It's part of active work\n\n**Demote to memory/ only when:**\n- Project completed\n- Person no longer frequent contact\n- Term rarely used\n\nThis keeps CLAUDE.md fresh and relevant.",
  "applicable_domains": [
    "productivity",
    "planning"
  ],
  "invocation": [
    "/memory-management"
  ],
  "tags": [
    "productivity",
    "anthropics",
    "knowledge-work"
  ],
  "authored_by": "anthropics",
  "source_url": "https://github.com/anthropics/knowledge-work-plugins/blob/main/productivity/skills/memory-management/SKILL.md",
  "lifecycle": "stable",
  "category": "governance",
  "provenance": {
    "source": "anthropics/knowledge-work-plugins",
    "source_url": "https://github.com/anthropics/knowledge-work-plugins/blob/main/productivity/skills/memory-management/SKILL.md",
    "author": "Anthropic",
    "license": "Apache-2.0",
    "notes": "Imported by scripts/import-anthropic-skills.py."
  }
}