What problem does it solve? Teams that keep documentation and code in separate repositories (open-source maintenance, multi-repo development, pre-publication projects) lack a consistent way to declare where code lives relative to docs. This Skill manages that workspace layout declaration so downstream workflows always know which directories are code roots. ## Core Features & Use Cases - Topology inspection: Returns a structured workspace context (mode, resolved absolute code-root paths, missing roots) that orchestration layers pass to other skills. - Interactive declaration maintenance: The reconcile entry asks the user for mode (inline/shell/linked) and code roots, writes the workspace: block into AGENTS.md frontmatter, and self-validates with rollback on failure. - Repository migration: Converts a single-repo project into a shell layout with git submodules, including detached-HEAD guards, pointer-drift repair, and fail-closed validation. - Use Case: You maintain a fork of an open-source project and want your private docs in a separate shell repo. Run the skill to declare the submodule as a code root, then migrate the repo layout without polluting the upstream repository. ## Quick Start Ask the assistant to inspect the current workspace topology and declare whether code lives inline, in submodules, or in linked external directories.