torquestatuslisted

# Torque Status Show the developer a unified view of their project state. No database — read files and git only. ## Procedure ### Step 1: Detect project type ```bash # Check which system is active ls -d .planning/ 2>/dev/null && echo "GSD_PROJECT=true" || echo "GSD_PROJECT=false" ls -d docs/plans/ 2>/dev/null && echo "SP_PROJECT=true" || echo "SP_PROJECT=false" ``` ### Step 2: GSD project state (if `.planning/` exists) Read these files in order (skip any that don't exist): 1. **`.planning/STATE.md`** — current phase, plan statuses, blockers 2. **`.planning/ROADMAP.md`** — milestone and phase overview 3. **`.planning/PROJECT.md`** — project goals and tech stack (first 30 lines) 4. **Active phase directory** — check `.planning/phases/N/` for the current phase: - `CONTEXT.md` — what this phase is about - `PLAN.md` or `PLAN-*.md` — execution plans and their status - `SUMMARY.md` files — completed plan summaries - `VERIFICATION.md` — verification results if phase is in verify stage - `HANDOFF.md` — if work was paused mid-phase ### Step 3: SP standalone state (if `docs/plans/` exists, no `.planning/`) 1. Read all `docs/plans/*.md` files 2. Check for completion markers (checked boxes `[x]` vs unchecked `[ ]`) 3. Identify current position in the plan ### Step 4: Git context ```bash git branch --show-current git log --oneline -5 git status --short ``` ### Step 5: Conflict detection Flag if BOTH `.planning/` AND `docs/plans/` exist — this is a misconfigurati