← ClaudeAtlas

archflow-migratelisted

Use ONLY when the user asks for /archflow-migrate or "archflow migrate". Upgrade a v1.0 archflow-onboarded project (sprints) to schema v2.0 (releases) — dry-run first, then apply
AZidan/archflow · ★ 27 · AI & Automation · score 81
Install: claude install-skill AZidan/archflow
> Arguments are the text after the skill name. # /archflow-migrate — Migrate a project from schema v1.0 to v2.0 Transforms an existing Archflow project's v1.0 roadmap into the v2.0 multi-file **release** model, using a deterministic engine (`scripts/migrate.py` in the plugin) — reconstructing real releases from git shipping evidence, not from sprints. Standalone command (NOT part of `onboard`). **Load-bearing idea: a sprint is NOT a release.** v1 sprints were agile time-boxes; many shipped nothing. The engine reconstructs releases from **git evidence** (deploy-pipeline landing, prod-branch merges, tags) and routes everything else to the backlog. Validated against real 3.4k–5.8k-line roadmaps. ## When it runs - **Manually:** the user runs `/archflow-migrate`. - **Auto-detected (prompt only, never auto-run):** any session where `.archflow/roadmap.yaml` has a `phases:` OR `sprints:` key, OR `schema_version` is absent/`"1.0"`: > "This project uses roadmap schema v1.0. Run `/archflow-migrate` to upgrade to v2.0." If `roadmap.yaml` already has `schema_version: "2.1"`, say it's already migrated and stop. ## How to run it (the deterministic engine) The migration is performed by **`.github/archflow/scripts/migrate.py`**, which ships with the plugin. It requires `python3` + `pyyaml`. Run it against the target project root. **1. DRY RUN first (writes nothing) — reconstruct + show the plan:** ```bash python3 .github/archflow/scripts/migrate.py --path <project-root> --dry-run