aif-fix

# Fix - Bug Fix Workflow Fix a specific bug or problem in the codebase. Supports two modes: immediate fix or plan-first approach. ## Workflow ### Step 0 (pre): Detect Handoff Mode Determine Handoff mode, task ID, and skip-review flag. If the caller passed `HANDOFF_MODE`, `HANDOFF_TASK_ID`, and `HANDOFF_SKIP_REVIEW` as explicit text in the prompt, use those values. Otherwise, use the Bash tool: ``` Bash: printenv HANDOFF_MODE || true Bash: printenv HANDOFF_TASK_ID || true Bash: printenv HANDOFF_SKIP_REVIEW || true ``` **Then check `HANDOFF_MODE`:** #### When `HANDOFF_MODE` is `1` (autonomous Handoff agent) The Handoff coordinator already manages status transitions and DB writes directly. Do NOT call MCP tools. Instead: - **No interactive questions:** Do not use `AskUserQuestion`. If `$ARGUMENTS` contains `--plan-first`, use "Plan first" mode. Otherwise default to "Fix now" mode. Always include tests and logging. - **Plan annotation (MANDATORY):** If `HANDOFF_TASK_ID` is non-empty, you MUST insert `<!-- handoff:task:<HANDOFF_TASK_ID> -->` as the very first line of the fix plan file, before the title. **Omitting this annotation when HANDOFF_TASK_ID is set is a bug — verify before completing.** This applies to both Step 1.1 (creating new plan) and any plan rewrite. #### When `HANDOFF_MODE` is NOT `1` (manual Claude Code session) Handoff sync is handled inline — see **Step 0.1** (after reading the fix plan file) for the task ID extraction and MCP sync trigger. The sync ...