torquenextlisted

# Torque Next Action Analyze project state and recommend exactly ONE next command. Think of this as a GPS for your development workflow. ## Procedure ### Step 1: Gather state Same as `/torque:status` — read `.planning/`, `docs/plans/`, git state. But don't output the full status. Focus on determining the current position. ### Step 2: Decision tree Work through this tree top-to-bottom. First match wins. ``` 1. Is there an active bug or failing test? → `systematic-debugging` Why: Bugs block everything. Fix first. 2. Does .planning/ exist? ├─ YES (GSD project): │ a. Is there a HANDOFF.md in the active phase? │ → `/gsd:resume-work` │ Why: Paused work should be resumed before starting new work. │ │ b. Is STATE.md showing a phase in "executing" with incomplete plans? │ → `/gsd:execute-phase` (continue) │ Why: Finish what you started. │ │ c. Is a phase complete but not verified? │ → `/gsd:verify-work` │ Why: Verification before review. │ │ d. Is a phase verified but not code-reviewed? │ → `requesting-code-review` │ Why: GSD has no review step — SP fills the gap. │ │ e. Is a phase reviewed but not shipped? │ → `/gsd:ship` or `/gsd:pr-branch` │ Why: Ship cleanly — filters .planning/ commits from PR. │ │ f. Are all phases in the current milestone complete? │ → `/gsd:audit-milestone` then `/gsd:complete-milestone` │ Why: Close out