speckit-repository-map

Read .specify/memory/repository-map.md to locate repository paths and ownership.

95|39|Updated Dec 15, 2025

Search Tags:#planning #multi-repo #spec-kit #repository-map #workspace-root #path-ownership

Ready to run

npx skills add https://github.com/liuminxin45/auto-podcast --skill speckit-repository-map

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-repository-map
Source: https://github.com/liuminxin45/auto-podcast/tree/main/.agents/spec-kit/skills/speckit-repository-map
Command: npx skills add https://github.com/liuminxin45/auto-podcast --skill speckit-repository-map

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill gives Spec Kit workflows a reliable way to find repository paths, roles, capability ownership, and affected rows without guessing from source trees.

Core Features & Use Cases

Fixed repository map lookup: Reads the workspace repository map as the source of truth for repository metadata.
Multi-repo planning support: Helps identify which repositories are relevant for specify, planning, and task scoping.
Path template guidance: Preserves relative templates for workspace and host paths so plans stay portable.
Use case: Use it when a stage needs to know which repository owns a capability or which rows are affected before inspecting code.

Quick Start

Ask the skill to read the repository map and return the workspace root, default branch, and affected repositories for the current Spec Kit task.

Frequently Asked Questions about speckit-repository-map

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

FAQPage Schema

How do I locate repository paths and ownership for Spec Kit multi-repo planning without scanning source trees?▼

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.

What is a repository map and how does it identify capability ownership in a multi-repo workspace?▼

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.

How do I find affected repositories and rows for a Spec Kit task before 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.

Can I use Spec Kit repository map lookup for multi-repo analysis if I only know the relative path templates?▼

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.

Does Spec Kit repository mapping require any dependencies or external components to locate workspace roots?▼

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.

What are the limitations of using a fixed repository map for path ownership instead of 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.