What problem does it solve? Projects onboarded with Archflow schema v1.0 organize work as sprints, but sprints are time-boxes that often shipped nothing, making it impossible to know what actually reached production. This Skill upgrades those projects to the v2.0 multi-file release model by reconstructing real releases from git shipping evidence instead of sprint boundaries. ## Core Features & Use Cases - Dry-run planning: Runs a deterministic Python engine in dry-run mode first, showing the detected v1 variant, deploy boundary, reconstructed release timeline, and warnings before writing anything. - Git-based release reconstruction: Detects deploy-pipeline boundaries and prod-branch merges to rebuild a true release history, routing shipped work to archived releases and unshipped work to the backlog. - Safe, reversible apply: Backs up the v1 roadmap to .archflow/backup-v1/, writes the v2.0 layout (roadmap index, backlog, release files, history), and enforces the one-active-release invariant. - Use Case: A team with a 5,000-line v1.0 roadmap.yaml containing dozens of sprints runs the migration to get a clean v2.0 structure where shipped features appear as archived releases and remaining work lands in a detailed backlog. ## Quick Start Ask the agent to run /archflow-migrate to dry-run the migration of your v1.0 Archflow project, review the reconstructed release plan, then confirm to apply it.
