overhaul

Scan a legacy repository to identify outdated content: old dependencies, deprecated APIs, legacy directory structures, and non-standard fragments; output a checklist for the plan skill.

Decision gate before analyze/plan: assess whether a legacy target is worth upgrading, maintaining at minimal cost, or retiring/replacing, by scoring technical state (T) and business value (B); produce a traceable assess report with explicit assumptions and a four-quadrant recommendation. Use it to avoid spending upgrade effort on systems that should be retired.

Based on the analyze report, produce an upgrade plan with risk grading and rollback strategy; requires user confirmation before the upgrade executes.

Batch-register legacy repositories from a CSV/JSON manifest and run them through the full analyze → plan → upgrade → verify pipeline as a queue; support serial / bounded-concurrency scheduling, failure retry (max 2), and interrupt resume (--resume), maintaining queue-level progress.

Aggregate upgrade results of many repositories (analyze/upgrade/verify reports and status files) into one unified summary report: overall progress, success/failure/skip statistics, risk aggregation, and leftover issues; support scoping by batch, all completed, or specific repositories.

Safety net executed when an upgrade batch fails or verify does not pass and cannot be quickly fixed: restore the target repository to its pre-upgrade baseline and re-verify baseline health. Use it explicitly from upgrade/queue failure paths before reporting failure.

Execute an approved upgrade plan against a legacy project: upgrade dependencies, restructure directories, and migrate code to the target conventions. Requires user-confirmed plan; creates branch/backup first and does not delete user data without explicit confirmation.

After an upgrade, run build, tests, static checks, and baseline comparison, then output a verification report with a pass/partial-pass/fail verdict.