memory-bank-manager

Maintains operational memory files and promotes durable engineering knowledge across sessions.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill memory-bank-manager-oleyna80
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: memory-bank-manager
Source: https://github.com/oleyna80/agentic-sdlc-framework/tree/main/skills/memory-bank-manager
Command: npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill memory-bank-manager-oleyna80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agent sessions lose context between runs, causing repeated mistakes, stale status notes, and lost engineering lessons. This Skill keeps the memory_bank/ directory concise and current while promoting durable knowledge to docs/engineering-memory/. ## Core Features & Use Cases - Session context tracking: Maintains context.md with current focus, working scope, and next step so any agent can resume work immediately. - Rolling progress log: Keeps progress.md up to date with a rolling window of up to 15 entries covering done, in-progress, and upcoming work. - Decision promotion: Records operational decision summaries in decisions.md and classifies reusable lessons at closeout as promoted, operational-only, or not-applicable. - Use Case: After a long debugging session, an agent updates the memory bank, promotes the root-cause analysis to docs/engineering-memory/, and the next session resumes without re-reading old chat history. ## Quick Start Update the memory bank with the current session status and promote any durable engineering lessons to the engineering memory docs.

Frequently Asked Questions about memory-bank-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep AI agent context between sessions?▼

Maintain a memory bank with a context file holding current focus, scope, and next step, plus a rolling progress log. The agent updates these files each session so any runtime can resume work without old chat history.

How to manage engineering decisions across multiple AI agents?▼

Record operational decision summaries in a decisions file and promote durable, cross-runtime lessons to a shared engineering memory directory. At closeout, classify each lesson as promoted, operational-only, or not-applicable.

What is the difference between memory bank and engineering memory?▼

The memory bank holds short-lived operational context and logs for the current work, while engineering memory stores durable decisions, source-of-truth chains, and reproducibility notes reusable by all agents over time.

How do I prevent stale notes in agent memory files?▼

Apply a no-rot rule: delete outdated wording, avoid duplicating the same status in multiple places, and keep the progress log to a rolling window of up to 15 entries.

When should a lesson not be promoted to durable memory?▼

Lessons that are purely operational to the current task or no longer applicable should be classified as operational-only or not-applicable at closeout instead of being promoted to the durable engineering memory.