🧠 Spec Kit Memory Hub

Durable project memory and context for AI-assisted development.

Spec Kit Memory Hub (memory-md) is a repository-native, Git-reviewable memory extension that provides AI coding assistants with persistent context across features. It ensures your agents reuse past architectural decisions, domain constraints, bug patterns, and lessons learned instead of repeating mistakes.

⚡ Core Value: Up to 10x Token Savings

Traditional systems either read the entire codebase (wasting thousands of tokens) or start every prompt from scratch. Memory Hub uses a three-tier architecture with an optional SQLite Caching Optimizer to compress context:

Why Developers and Teams Use It:

• Up to 10x Token Reduction: Replaces broad codebase context dumps with highly compressed, 900-word targeted synthesis.
• Prevent Recurring Bugs: Ensures a bug solved in Feature #2 is never reintroduced in Feature #5.
• Seamless Onboarding: New developers and AI agents immediately inherit the project's historical memory.
• Zero-Leak Privacy: Global cross-project sync operates entirely locally using SHA-256 project path anonymization.

🚀 Quick Start in 3 Steps

1. Install the Extension

Add the extension to Spec Kit CLI (either from the official registry, a release artifact URL, or a local directory):

From the Registry (Recommended):

specify extension add memory-md

From a Release Artifact (ZIP):

specify extension add memory-md --from https://github.com/DyanGalih/spec-kit-memory-hub/archive/refs/tags/v0.9.2.zip

From a Local Developer Artifact:

specify extension add memory-md --dev /path/to/spec-kit-memory-hub

2. Bootstrap Your Project

Initialize the folder structure and instructions inside your repository:

/speckit.memory-md.init

This creates:

• docs/memory/ — Permanent, Git-tracked project memory templates.
• .github/copilot-instructions.md — Active agent workflow context.
• .specify/extensions/memory-md/config.yml — Customizable extension settings.

3. Profile Stack sync channels

Profile the repository's technologies to subscribe to cross-project shared lessons:

/speckit.memory-md.init-project

🛠️ Memory Commands Directory

🔌 Native Model Context Protocol (MCP) Server

Memory Hub includes a native, fully-compliant Model Context Protocol (MCP) Server. This allows modern LLM clients (such as Claude Desktop, VS Code Cline, Roo-Cline, Cursor, etc.) to query, synthesize, share, and sync memory directly via JSON-RPC, without needing to execute terminal CLI subprocesses.

Key MCP Tools Exposed to Your Agent:

• speckit_memory_search: Fast SQLite-cached semantic search across local project memories.
• speckit_memory_synthesize: Directly generates a 900-word compressed memory-synthesis.md context file.
• speckit_memory_share_lesson: Elevates and publishes an approved local lesson into the global local database.
• speckit_memory_sync_shared: Pulls matching technology stack lessons into docs/memory/SHARED_LESSONS.md with interactive review banners.
• speckit_memory_init_project: Profiles active project languages/frameworks to configure sync channels.

To start the server, configure your client to run the mcp-start command:

npx -y speckit-memory mcp-start

*For complete configurations for Claude Desktop, Cline, and other IDE client settings, see the SQLite & MCP Architecture Guide.*

📚 Technical Documentation Map

We have split the Spec Kit Memory Hub manual into focused technical resources:

spec-kit-memory-hub/
├── README.md                           ← Highly readable, high-level project summary
└── docs/
    ├── value-proposition.md             ← Business case: Team velocity, alignment, and 10x token ROI
    ├── governed-memory-workflow.md      ← Integration guides for Architecture Guard governed pipelines
    ├── reference-manual.md              ← Detailed specs: File formats, CLI command list, and config schemas
    ├── sqlite-mcp-architecture.md       ← Blueprints: SQLite cache, Model Context Protocol (MCP), and global sync
    ├── first-ten-minutes.md             ← Step-by-step developer walkthrough for bootstrapping a new project
    └── optimizer-roadmap.md             ← Execution roadmap: SQLite Phase 1-4 and Phase 3.5 milestones

Direct Links:

• 🧠 Value Proposition & ROI — Deep-dive on team velocity, alignment gains, and exact token benchmarks.
• 🛡️ Governed Memory Workflow — Best practices for combining Memory Hub with Architecture Guard and Security Review validation gates.
• 📘 Reference Manual — File schema layouts, available prompts, environment variables, configuration properties, and IDE agent settings.
• 🔌 SQLite & MCP Architecture — Architectural details of the local optimizer, exposed Stdio MCP JSON-RPC tools, and anonymized sync protocols.
• ⏱️ First 10 Minutes: Concrete Example — Practical developer walkthrough from /init through context planning.
• 🗺️ Technical Roadmap — The active development roadmap across SQLite, MCP, and high-performance hybrid indexing.

⚖️ Design Philosophy

• Curated, Not Automatic: Memory capture requires human approval; we keep permanent memory pristine.
• Visible in Git: All decisions and lessons are fully tracked in Git history, not hidden in local app state.
• Specs Remain Clean: Specifications define the active target; Memory Hub captures durable past constraints.
• AI Complements Thinking: The agent prepares synthesis context, but developers review and authorize all changes.