What problem does it solve?
Provides a systematic, phased approach to upgrading npm dependencies across one or more packages while minimizing breakage and ensuring each major version bump is validated before proceeding. It prevents sweeping, error-prone updates by enforcing single-major-step progress, clear validation gates, and explicit engineer approval points.
Core Features & Use Cases
- Phased upgrade workflow: Assess, baseline, research, execute phased updates, validate, engineer gate, and record progress for multi-session upgrades.
- Strict validation gates: Require zero TypeScript errors, zero ESLint errors, all tests passing, and a successful production build (engineer-run) before advancing.
- Peer dependency resolution and coupled-updates guidance: Recommendations for packages that must be updated together, override usage as a last resort, and migration research protocol.
- Multi-session memory and communication: Templates and a memory file format to track progress across sessions and structured reporting for handoffs.
Quick Start
Run a phased upgrade by assessing npm outdated, pinning a clean baseline, updating the smallest safe set of major versions, running AI-led tsc/lint/tests, and requesting the engineer to run the production build before proceeding.