migratelisted

Inventory an existing spec-driven project and apply bounded migrations to jig defaults: `report`, `adopt-layout`, `rename-decisions`, `split-slices`, slice-to-spec, `seed-decisions`, and `copy-machinery`. Use when the user says migrate this project to jig, adopt jig here, this repo already has specs — set up jig, scaffold-init refused — what now; introduce jig to an existing codebase; apply ADR-0004 to my project; migrate flat slices into nested specs; seed the lightweight-decisions home; or copy jig's machinery into my project. Reports are read-only; mutations support dry runs where available, refuse conflicts before writing, and preserve originals in the agentic slice-to-spec workflow.
ramboz/jig · ★ 4 · AI & Automation · score 73

Install: claude install-skill ramboz/jig

> Codex adapter note: `rename-decisions` and `copy-machinery` are host-aware. Use `--host codex` when running them from Codex-facing docs or source checkouts; helpers copied under `.codex/skills/` infer Codex by default. > Spec 008 created this skill from scratch. The deterministic filesystem > walk + verdict logic + report rendering live in `migrate.py`; this > SKILL.md drives the judgment layer (when to invoke, how to interpret > ambiguities, what operations to suggest in what order). ## What this skill does Closes the "already spec-driven" gap that `scaffold-init` doesn't handle: projects that organically grew the same workflow jig codifies but landed on different conventions (folder names, filename prefixes, slice topology). Direct example: a project with `docs/slices/` (flat) and `docs/decisions/` (validator-style) — `scaffold-init` would not detect it as scaffolded and would either refuse confusingly or pollute the tree. `migrate` flips that around: detect existing shape first, then propose a migration plan, then (in later slices) apply the rename / restructure operations. `migrate.py` exposes six subcommands: - `report` — strictly read-only inventory + plan. - `adopt-layout` — validates an existing custom-root corpus and writes only its `scaffold.json` sentinel/config; supports `--dry-run`. - `rename-decisions` — applies ADR-0004's rename. Idempotent; refuses on conflict; has a `--dry-run` mode; use `--host codex` when running from Codex-facing source or plugin p