Repo brief
One-page orientation for what the system does, how it runs, and where to start.
Overview
A sharper way to understand unfamiliar codebases
Most delivery teams lose time because repo notes, open questions, and system evidence live in five different places. 221B brings that work into one operating surface so consultants and agents can move from confusion to a grounded recommendation quickly.
- Investigation method and evidence grading docs
- Repo brief, scorecard, open questions, and decision log templates
- MCP server for docs and repo registry search
- Registry format for tracking active repositories
Best Fit
Who this product is built for
- Consultants dropped into unfamiliar client systems
- Technical due diligence and repo discovery work
- Internal platform teams documenting delivery risk
- AI agents that need grounded repo context
Artifacts
The outputs teams actually use
These are the delivery artifacts the repo is designed to produce, not just the internal implementation detail.
System map
A fast technical picture of flows, dependencies, and likely change points.
Decision trail
Explicit record of risks, open questions, and calls made during investigation.
Workflow
How it gets used in real delivery
Each product is designed to slot into a fixed-scope Baker Street engagement rather than sit as a disconnected side project.
Intake the repository, define the delivery question, and capture the first-pass start-here files.
Map the core flow with evidence-backed notes, not generic architecture guesses.
Publish a reusable report that humans and MCP clients can both consume.
Next Move
Use it alongside the rest of the Baker Street system
See the delivery stack
Move from product detail into the related package, workflow, or delivery stack page.
Explore packages
Move from product detail into the related package, workflow, or delivery stack page.
GitHub repo
Move from product detail into the related package, workflow, or delivery stack page.
Product Intake
Need a system understood before work begins?
Bring the repo, the delivery question, and the deadline. Baker Street uses 221B when a team needs grounded technical orientation before it commits scope or budget.