hatch3r-feature

> **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. # Feature Implementation Workflow ## Quick Start ``` Task Progress: - [ ] Step 0: Detect ambiguity (P8 B1) - [ ] Step 1: Read the issue and all relevant specs - [ ] Step 1c: Design System Inventory (if UI) — invoke `hatch3r-design-system-detect` - [ ] Step 2: Produce an implementation plan - [ ] Step 2b: Test-first approach (TDD alternative — optional) - [ ] Step 3: Implement the vertical slice - [ ] Step 4: Write tests (unit, integration, security, E2E) - [ ] Step 5: Verify quality gates - [ ] Step 5b: Browser verification (if UI) - [ ] Step 5c: UI/UX Verification Gate (if UI) — invoke `hatch3r-ui-ux-verify`; all 9 gates must pass before Step 6 - [ ] 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 files, 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: acceptance criteria incomplete or untestable, data shape or error behavior unspecified, UI states (loading/empty/error/partial) undefined, security/entitlement model unstated, or the change requires a schema/API migration with downstream con...