work-issuelisted

# Work Issue — GitHub Issue-Driven Development Orchestrate the full lifecycle of a GitHub issue: analysis → branch → plan → TDD implementation → verification → automated acceptance testing → review → PR. **Invocation:** `/work-issue 83` (single issue) or `/work-issue 83 91 145` (batch — process sequentially) **Optional flags** (single-issue mode only): - `--phase` — force phased-execution for the implementation portion (Phase 4). Skips auto-detection. - `--no-phase` — skip phasing entirely. Runs Phase 4 as TDD regardless of plan size. - (no flag) — runs conservative auto-detection at Phase 3.5; phasing only if both quantitative + self-assessment gates agree. Example: `/work-issue 83 --phase` ## Instructions When invoked, extract the issue number(s) from the argument string. If multiple numbers are provided, process them one at a time in order. For each issue, execute the 8 phases below **in strict sequence**, stopping at each gate for user approval. ### Gate Prompt Convention At every gate, use `AskUserQuestion` to present structured options instead of free text. This lets the user press Enter to continue (the default), or pick an alternative action. Each gate's options are tailored to the phase, but the pattern is always: - **Option 1** = Continue to next phase (Recommended) — always the default - **Options 2-3** = Phase-appropriate alternatives (e.g., review diff, modify ACs, skip phase) - **Option 4** = Abort workflow - The user can always select "Other" (built int