memory-bank

Store project decisions, goals, and context in structured Markdown files.

Updated Dec 22, 2025
One-click install
npx skills add https://github.com/0xkynz/codekit --skill memory-bank-0xkynz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-bank
Source: https://github.com/0xkynz/codekit/tree/main/templates/skills/memory-bank
Command: npx skills add https://github.com/0xkynz/codekit --skill memory-bank-0xkynz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Memory bank preserves project knowledge across sessions by creating and maintaining structured Markdown files that capture decisions, context, and progress, so your work can resume seamlessly after resets.

Core Features & Use Cases

  • Provides a dedicated memory-bank/ structure with core files (projectbrief.md, productContext.md, activeContext.md, systemPatterns.md, techContext.md, progress.md) to anchor project knowledge.
  • Supports session workflows: starting a memory bank, updating context, and ending a session with a fresh status summary, enabling cross-team collaboration and long-term continuity.
  • Facilitates documentation-driven memory, enabling quick onboarding, audits, and knowledge transfer across contributors.

Quick Start

Create memory-bank/ and initialize core files, then regularly update activeContext.md and progress.md to keep context current.

Frequently Asked Questions about memory-bank

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

FAQPage Schema
How do I preserve project context across sessions after a reset?

A memory bank preserves project context across sessions by structuring Markdown files like activeContext.md and progress.md. You update these files during session workflows to capture decisions, ensuring work resumes seamlessly after resets.

What is a memory bank and how does it maintain project knowledge?

A memory bank maintains project knowledge by storing decisions, goals, and context in structured Markdown files. It anchors critical information across long-running software projects, enabling quick onboarding and cross-team knowledge transfer.

How do I set up a documentation workflow for long-running software projects?

To set up a documentation workflow, create a memory-bank directory and initialize core Markdown files like projectbrief.md and techContext.md. Regularly update activeContext.md and progress.md to keep project context current across contributors.

Can I use a memory bank for cross-team collaboration and knowledge transfer?

Yes, a memory bank supports cross-team collaboration by maintaining a shared knowledge base of structured Markdown files. Files like systemPatterns.md and productContext.md capture collective decisions, enabling quick onboarding and seamless knowledge transfer across contributors.

What files do I need to start a memory bank for session continuity?

Starting a memory bank requires creating a directory with six core Markdown files: projectbrief.md, productContext.md, activeContext.md, systemPatterns.md, techContext.md, and progress.md. These files anchor project knowledge and ensure session continuity.