What problem does it solve? Project documentation like ADRs, runbooks, troubleshooting notes, and lessons learned often lives in a personal knowledge store (Obsidian vault, Confluence, Notion), making repositories incomplete and hard to share. This Skill onboards a repository to the knowledge-placement model by moving build/operate docs into the repo's docs/ directory while leaving cross-project knowledge in the store. ## Core Features & Use Cases - Structured docs migration: Copies ADRs, architecture notes, lessons, runbooks, and troubleshooting docs into docs/adr, docs/architecture, docs/lessons, docs/runbooks, and docs/troubleshooting with modular index files. - Cross-reference rewriting: Rewrites links so moved artifacts use relative repo paths while store-only artifacts become plain-text provenance, enforcing the rule that the store links out to repos but never the reverse. - Store-side stubbing and verification: Replaces moved store notes with pointer stubs so inbound wikilinks still resolve, then verifies no live store links remain in docs/ before committing and opening a PR. - Use Case: Onboard an existing repository whose ADRs and runbooks live in a personal vault so the repo becomes self-contained and share-ready for collaborators and agents. ## Quick Start Ask the agent to onboard this repository to the knowledge-placement model by moving its ADRs, runbooks, and lessons from the vault into the repo's docs directory.
