memory-management
Resolves project shorthand, acronyms, nicknames, and internal names using durable memory and docs. Use when the goal contains unexplained acronyms, nicknames, or team jargon that must be decoded befor
SKILL.mdskills/memory-management/SKILL.md
GitHubMemory Management
Decode shorthand so plans use the team's real names and constraints.
Workflow
- Extract terms — acronyms, nicknames, ticket IDs, service aliases from the goal.
- Resolve — check project memory notes,
AGENTS.md/CLAUDE.md, domain glossaries (CONTEXT.md), ADRs, and recent docs. Seereferences/resolution-order.md. - Disambiguate — if a term maps to multiple meanings, state candidates and pick with evidence (or ask only if blocked).
- Normalize — rewrite the goal/plan using canonical names.
- Capture (optional) — if a stable new alias was confirmed, propose a one-line memory entry for the user to keep — do not invent long-lived memory without confirmation when project rules require it.
Constraints
- Prefer written project sources over model prior knowledge for internal names.
- Do not invent expansions for unknown acronyms; mark
[UNKNOWN: term]and continue with unblocked work. - Keep memory entries short and factual.
Verification
- All critical shorthand resolved or marked unknown
- Plan uses canonical names
- Sources cited for non-obvious expansions