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 before planning. Do not use for general research synthesis (use synthesize-research).From its SKILL.md
npx -y skills add IcodeNet/agent-skills --skill memory-managementAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, 260 tokens by cl100k_base, as published. Nobody here has run it
Memory 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
What ships with it: 1 file
420 B alongside SKILL.md
references/
- resolution-order.md420 B