What problem does it solve? Teams working across multiple repositories lose track of which repos participate in a capability, how they depend on each other, and where the canonical documentation lives. This Skill indexes that architecture once so future agents and engineers can orient from docs/resources/<area>/ instead of rediscovering repo relationships, package names, install modes, and runtime dependencies. ## Core Features & Use Cases - Area Summary Generation: Writes a structured summary.md covering responsibility, participant repos, boundaries, runtime modes, known docs, and open questions. - Dependency Graph Mapping: Produces dependency-graph.md with repo edges, runtime versus development relationships, install modes, and drift signals that trigger context refreshes. - Registry and System-Map Alignment: Uses repo slugs from .config/repos.project.md, optionally registers task-area prefixes in docs/tasks_manager/_areas.md, and updates docs/resources/system-map.md when the capability picture changes. - Use Case: A platform team spanning a runtime repo, an SDK repo, and a docs repo asks to "define the billing-platform area"; the Skill inspects manifests, Dockerfiles, and lockfiles across checkouts and writes evidence-backed area docs with explicit unknowns instead of guesses. ## Quick Start Ask the agent to define the area for your capability, for example: "Define the search-indexing area across these repos and write its summary and dependency graph."
