What problem does it solve? AI coding sessions lose project context between runs, forcing models to re-read code or guess at contracts. This Skill builds and maintains a persistent, evidence-anchored knowledge base under the project-root wiki/ folder so future ORC runs consult verified docs instead of model priors. ## Core Features & Use Cases - Codebase scanning to docs: Dispatches pinned scanner agents (Opus 4.8 high) to write wiki/orc-feature-, wiki/orc-reference-, and orc-architecture-overview.md docs whose claims are anchored to real files, with freshness computed on read from git commit distance. - Deterministic registration: Runs the orc wiki sync CLI to derive wiki/INDEX.md and .claude/orc/wiki-meta.json from doc headers, so a paused multi-session scan still leaves a valid, indexed wiki. - Cross-repo crosslink: Publishes per-endpoint boundary tags and resolves consumed contracts from linked sibling repos, with advisory drift warnings and a federation atlas. - Use Case: After a large feature ships, run a targeted refresh so only the docs whose covered files changed are re-scanned, keeping the knowledge base current without paying for a full re-scan. ## Quick Start Ask the assistant to run /orc-wiki to scan this codebase and build the project knowledge base, approving the cost warning when prompted.