team-fixlisted

# Team Fix — Bug Fix Pipeline Run the compressed bug-fix pipeline. Goes straight to test-driven fix discipline without the full QRSPI ceremony. ## Input `$ARGUMENTS` may be: - A ticket identifier (e.g. `ENG-1234`) — set aside as `ticketId` on `task.md`. - An issue URL — fetched through `gh issue view` to extract title and body. - Free-form text — treated as the bug description. When `$ARGUMENTS` is empty, **discover, do not demand**: ground in repo context before asking. Read recent `git log` activity and the repo's `README` / `CLAUDE.md` to surface the likely failing area, then use `AskUserQuestion` with labeled options to fill any genuine gap. Never bare-stop with a plain "describe the bug" demand when context is available. ## When to Use Use `/team-fix` when: - The bug is well-understood and the affected code is known - The fix is likely contained to a small number of files - No architectural decisions are needed — this is a defect correction Use `/team` (full QRSPI pipeline) when: - The root cause is unknown and needs investigation - The fix requires designing new behavior or APIs - Multiple subsystems may be involved - The user wants to align on the approach before code is written ## Pipeline ``` WORKTREE → REPRODUCE → RED (failing test) → GREEN (minimal fix) → VERIFY → SHIP ``` No Question. No Research. No Design. No Structure. No Plan. No approval gate. ## Setup 1. **Resolve the input** to a bug description first. On empty `$ARGUMENTS`, ground in re