map-codebase

Documenting an unfamiliar codebase for onboarding requires a structured discovery pass across multiple dimensions to extract project structure, entry points, dependencies, and deployment context into a shareable factual context brief.

A codebase context brief is a standardized factual summary of a repository's architecture. Generate one during onboarding, planning, debugging, or architecture reviews of unfamiliar repositories to provide immediate downstream context.

Generate a codebase architecture summary by orchestrating a five-dimension discovery workflow. This process outputs a concise, actionable context brief to a default file path and updates your session tracking file with progress and decisions.

Yes, you can use a structured codebase discovery workflow for architecture reviews. It applies a five-dimension discovery pass to identify project structure and deployment context, outputting a factual brief suitable for evaluating architecture.

No specific dependencies are required to map a codebase and produce a context brief. The workflow independently identifies existing dependencies and deployment context, saving the output to a default markdown path without external tools.

The best way to prepare an unfamiliar repository for flow planning is to map the codebase first. This generates a factual context brief at the default output location, which downstream flow planning and arch-review steps can directly consume.