What problem does it solve? Moving a living spec between central storage (capabilities/<name>/spec.md) and colocated storage (next to the code it describes) requires moving files and updating the living-specs.yml registry atomically; doing either by hand leaves the config and disk disagreeing, which fails the entire living-specs configuration. ## Core Features & Use Cases - Guided relocation with a review gate: Resolves each capability's current layout and target path, shows the planned move, and pauses for confirmation before touching anything. - Atomic helper execution: Runs relocate-capability.py to move the spec plus any .arch.md or .coverage.md tier siblings and rewrite the registry in one reversible operation. - Post-move verification: Confirms with resolve-spec-paths.py that the resolver reports the new spec path and that most-specific-first glob ordering is unchanged. - Use Case: A team decides the billing spec should live next to its code. The skill previews capabilities/billing/spec.md → src/billing/billing.spec.md, flags the display-name change, and completes the move with registry and verification intact. ## Quick Start Move the billing capability's living spec to colocated storage and verify the registry stays in sync.
