torquemigratelisted

# Migrate to Meridian Evaluate whether the current project would benefit from upgrading to [Meridian](https://github.com/mattjaikaran/meridian) and provide a migration path. ## What is Meridian? Meridian is the standalone successor to Torque. Instead of routing between GSD and Superpowers, Meridian IS the system — a SQLite-backed state machine with 39 commands, deterministic resume, quality gates, and remote agent dispatch. ## When to Migrate ### Signals you've outgrown Torque Run through this checklist. If 3+ are true, Meridian is the right move. - [ ] **Session continuity is painful** — you lose context between sessions and `/gsd:resume-work` isn't enough - [ ] **Multi-milestone project** — you've completed 1+ milestones and are starting another - [ ] **Team coordination** — multiple people or AI agents need to work on the project - [ ] **You want deterministic resume** — same state should produce the exact same prompt every time - [ ] **You need board sync** — Linear, Jira, or similar needs to stay in sync with phases - [ ] **Remote execution** — you want to dispatch plans to other machines or agents - [ ] **Execution learnings** — you want the system to learn from failures and improve over time - [ ] **You're fighting the routing** — GSD and SP conflict resolution is becoming overhead ### Stay with Torque if - Project is simple (< 3 milestones expected) - You like GSD and Superpowers separately and just need them coordinated - You don't need persistent state beyo