mb-map-codebase

Map an existing codebase into Memory Bank baseline artifacts.

53|11|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/mrvladd-d/memobank --skill mb-map-codebase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mb-map-codebase
Source: https://github.com/mrvladd-d/memobank/tree/main/skills/mb-map-codebase
Command: npx skills add https://github.com/mrvladd-d/memobank --skill mb-map-codebase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Map an existing codebase into Memory Bank as-is, without introducing backlog items.

Core Features & Use Cases

  • Scans repository root to produce as-is MB docs: product, architecture, runbooks, contracts, and testing.
  • Merges evidence from scoped workers to reflect the current system without speculative backlog.
  • Outputs ready-to-sail MB artifacts that support PRD deltas and MB-SYNC.

Quick Start

Run the mb-map-codebase process from the repository root to generate as-is Memory Bank baselines.

Frequently Asked Questions about mb-map-codebase

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

FAQPage Schema
How do I baseline an existing codebase into Memory Bank documentation?

To baseline a codebase into Memory Bank, you run the mapping process from the repository root to scan existing code and generate as-is documentation artifacts like product, architecture, runbooks, contracts, and testing files without adding backlog items.

What is codebase mapping for brownfield repositories?

Codebase mapping for brownfield repositories scans existing project files to establish a Memory Bank baseline, reflecting the current system architecture and product state accurately without introducing speculative development backlog.

Do I need a pre-initialized skeleton before mapping a codebase to Memory Bank?

Yes, codebase mapping relies on a pre-initialized .memory-bank skeleton to function properly. This existing directory structure is required to store the generated product, architecture, runbooks, contracts, and testing documentation.

What documentation artifacts are generated when scanning a repository for Memory Bank?

Scanning a repository generates baseline Memory Bank documentation artifacts including product documentation, architecture details, runbooks, contracts, and testing records that capture the current state of the system as evidence.

How do Memory Bank baselines support future PRD deltas and sync steps?

Memory Bank baselines record evidence from scoped workers to reflect the current system, providing the foundational as-is documentation needed to calculate PRD deltas and execute downstream MB-SYNC operations effectively.

Can I generate Memory Bank artifacts without creating speculative backlog items?

Yes, the codebase mapping process explicitly produces as-is Memory Bank artifacts by merging evidence from scoped workers, reflecting the current system state without introducing speculative backlog items into the repository.