What problem does it solve? Teams working across multiple repositories lose track of how repos, capability areas, and cross-repo flows fit together, especially after teammates change code or docs. This Skill builds and maintains a single status-aware index so architecture knowledge stays current and evidence-backed. ## Core Features & Use Cases - System Map Generation: Creates or refreshes docs/resources/system-map.md covering participant repos, capability areas, critical flows, cross-repo boundaries, drift signals, and open questions. - Lifecycle Status Tracking: Labels every repo, area, flow, and boundary as draft, accepted, partially-implemented, implemented, or superseded, with evidence required for implemented claims. - Drift Detection: Runs focused refresh passes after teammate changes, reconciling the map against task history, contracts, and execution logs. - Use Case: After a teammate merges changes across three services, ask for a drift check to update the system map, flag stale area docs, and record open questions for follow-up tasks. ## Quick Start Ask the agent to map the system and refresh docs/resources/system-map.md for all configured repos.
