speckit-repository-map

To locate repository paths and ownership for multi-repo planning, read the .specify/memory/repository-map.md file. This fixed repository map serves as the source of truth for repository metadata, eliminating the need to scan source trees for path identification.

A repository map is a fixed markdown file that defines repository roles and capability ownership across a multi-repo workspace. It works by reading .specify/memory/repository-map.md to match repository paths with their affected rows and capabilities without inspecting code.

Find affected repositories and rows by querying the repository map lookup process. It reads the fixed Spec Kit map at .specify/memory/repository-map.md to identify affected repositories and rows, returning the workspace root and relevant paths before any code inspection occurs.

Yes, you can use repository map lookup for multi-repo analysis with relative path templates. The process preserves relative templates for workspace and host paths to keep plans portable, reading the fixed map to identify relevant repositories without absolute path dependencies.

Spec Kit repository mapping requires no dependencies or external components to locate workspace roots. It relies solely on reading the .specify/memory/repository-map.md file as the source of truth, preserving relative path templates and handling uncertainty without scanning source trees.

The limitation of a fixed repository map is that it requires the .specify/memory/repository-map.md file to be manually maintained as the source of truth. It handles uncertainty during lookup but cannot detect repository changes dynamically, unlike scanning source trees for path ownership.