blueprint-map

Map a brownfield repository into a seven-artifact codebase bundle.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/rakole/blueprint --skill blueprint-map
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blueprint-map
Source: https://github.com/rakole/blueprint/tree/main/skills/blueprint-map
Command: npx skills add https://github.com/rakole/blueprint --skill blueprint-map

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Maps a brownfield repository into a stable, seven-artifact codebase bundle with evidence-backed outputs to guide reuse-versus-refresh decisions during Blueprint lifecycle.

Core Features & Use Cases

  • Evidence-backed codebase mapping to produce canonical artifacts in the .blueprint/codebase/ directory, enabling repeatable governance and planning.
  • Supports reuse-versus-refresh decisions by comparing against canonical contracts and existing bundle state, then drafting repair or refresh steps.
  • Produces a seven-document artifact bundle (STACK.md, STRUCTURE.md, ARCHITECTURE.md, CONVENTIONS.md, TESTING.md, INTEGRATIONS.md, CONCERNS.md) to codify the brownfield mapping results and drive downstream workflows.
  • Provides a runtime contract and references to guidance in map-runtime-contract.md to ensure consistent authoring and validation.

Quick Start

Invoke the /blu-map-codebase command on your repository to generate the initial codebase bundle.

Frequently Asked Questions about blueprint-map

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

FAQPage Schema
How do I map a brownfield codebase with evidence-backed artifacts?

Map a brownfield repository by generating a seven-artifact codebase bundle that codifies existing structure, architecture, conventions, and concerns. This approach captures the current state of an undocumented codebase using repo-relative inputs to produce canonical, evidence-backed documentation.

What is included in the artifact bundle for codebase mapping?

The artifact bundle includes seven markdown documents: STACK.md, STRUCTURE.md, ARCHITECTURE.md, CONVENTIONS.md, TESTING.md, INTEGRATIONS.md, and CONCERNS.md. These canonical artifacts codify mapping results to drive downstream governance workflows and planning.

When do I need to generate a codebase artifact bundle for repository analysis?

Generate a codebase artifact bundle when facing reuse-versus-refresh decisions during Blueprint lifecycle workflows. It provides evidence-backed outputs comparing canonical contracts against existing bundle state to justify repair or refresh steps.

Can I refresh existing codebase artifacts instead of regenerating the entire bundle?

Yes, artifact refresh is supported by comparing against canonical contracts and existing bundle state to draft repair or refresh steps. This enables targeted updates to specific artifacts without regenerating the entire seven-document bundle.

Does codebase mapping work with MCP tooling for persisting results?

Codebase mapping persists results through MCP tooling to satisfy the map runtime contract. The runtime contract and guidance references ensure consistent authoring and validation of canonical artifacts across the repository analysis workflow.

What are the limitations of brownfield repository mapping for governance workflows?

Brownfield repository mapping is limited to producing canonical artifact prose from repo-relative inputs. It requires a valid runtime contract and depends on MCP tooling for persistence, meaning offline or non-contract environments may not support consistent validation.