hatch3r-bug-fix

> **Note:** Commands below use `npm` as an example. Substitute with your project's package manager (`yarn`, `pnpm`, `bun`) or build tool when your project uses a different package manager. # Bug Fix Workflow ## Quick Start ``` Task Progress: - [ ] Step 0: Detect ambiguity (P8 B1) - [ ] Step 1: Read the issue and relevant specs - [ ] Step 2: Produce a diagnosis plan - [ ] Step 2b: Browser reproduction (if UI bug) - [ ] Step 2c: Test-first approach (TDD alternative — optional) - [ ] Step 3: Implement minimal fix - [ ] Step 4: Write regression test - [ ] Step 5: Verify all tests pass - [ ] Step 5b: Browser verification (if UI bug) - [ ] Step 6: Open PR ``` ## Step 0 — Detect Ambiguity (P8 B1) Before any work, scan the invocation for unresolved questions in scope, intent, acceptance criteria, target environment, or irreversibility. If any are found, ask the user via the platform-native question tool per `agents/shared/user-question-protocol.md`. Do not proceed under silent assumption. Default path, not an exception. Triggers for THIS skill: reproduction steps incomplete, expected vs actual behavior unstated, severity unclear (P0/P1 vs P2/P3), affected environment unknown (staging vs prod), or fix may require schema/API change with downstream consumers. ## Step 1: Read Inputs - Parse the issue body: problem description, reproduction steps, expected/actual behavior, severity, affected area. - Read relevant project documentation based on affected area (see spec mapping in pro...