Menu
Loom root entry for detection, diagnosis, metadata-only adoption, and scenario routing.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Confirm current-head host attestation, hosted delivery gate, required checks, and mergeability.
Confirm current-head host attestation, hosted delivery gate, required checks, and mergeability.
Adopt a repository through Loom metadata and verify the global runtime provider.
Execute a bounded Work Item after host-native admission and before pre-review.
Prepare a session handoff from public derived state without repository mutations.
Loom root entry for detection, diagnosis, metadata-only adoption, and scenario routing.
| name | loom-init |
| description | Loom root entry for detection, diagnosis, metadata-only adoption, and scenario routing. |
Use this root scenario to detect the repository state and choose one bounded next scenario. It does not create execution carriers or guess a current item.
loom detect --target <repo> --json.loom doctor --target <repo> --json when installation or provider
readiness is uncertain.loom-adopt.loom status, loom workspace check, or loom route.Repository adoption is metadata-only. Reinforced governance may strengthen host review and validation, but never restores repo work-item, progress, current, review, spec, shadow, or closeout carriers.
Finish when the next scenario, typed subject, formal worktree, and validation boundary are explicit. See ../route-matrix.md.