What problem does it solve? Long-running projects across multiple repositories lose context: subsystem maps, architectural decisions, and cross-repo API contracts live nowhere durable, and agents re-derive them expensively or trust stale notes. This Skill defines conventions for storing that knowledge in an Obsidian vault without letting unbounded notes blow up the context window. ## Core Features & Use Cases - Vault layout conventions: Standardizes paths for repo codemaps, decision records, and cross-repo contracts, plus a single INDEX.md entry point. - Index-first reading rule: Only INDEX.md is read by default; all other notes are fetched by path on demand to keep token usage bounded. - Anchor-based staleness detection: Every note carries an anchor: <repo>@<sha> so git diff can reveal when referenced files moved and the note needs re-verification. - Use Case: A team with 5+ repos records that service A's endpoint is consumed by service B in a way neither repo's code shows; the contract note in contracts/ captures it, and anchors catch when it drifts. ## Quick Start Set up an Obsidian vault for project memory with an index, codemap mirrors, and anchored decision notes following the crew-memory conventions.