hatch3r-issue-workflow

# Issue Workflow ## Quick Start When assigned an issue or work item (GitHub Issue, Azure DevOps Work Item, or GitLab Issue — check `platform` in `.hatch3r/hatch.json`), follow these 8 steps in order: ``` Task Progress: - [ ] Step 0: Detect ambiguity (P8 B1) - [ ] Step 1: Parse the issue - [ ] Step 2: Load the issue-type skill - [ ] Step 3: Read relevant specs - [ ] Step 4: Produce a plan - [ ] Step 5: Implement - [ ] Step 6: Test - [ ] Step 6b: Browser verification (if UI) - [ ] Step 7: Open PR - [ ] Step 8: Address review ``` ## 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. This upgrades the existing Escalation block from exception to default. Triggers for THIS skill: issue type unclear (bug vs feature vs refactor), acceptance criteria missing or contradictory, scope boundary undefined, irreversible operation in path (schema change, public API rename), and target branch / merge policy ambiguous. ## Step 1: Parse the Issue - Read all fields from the issue template. - Identify: type (bug/feature/refactor/qa), affected area, priority, acceptance criteria. - Note linked issues and spec references. ## Step 2: Load the Issue-Type Skill Navigate to the matching ...