hatch3r-hooks

# Hooks — Event-Driven Agent Activation ## Quick Start ``` Task Progress: - [ ] Step 0: Detect ambiguity (P8 B1) - [ ] Step 1: Discover current state - [ ] Step 2: Define a hook (add) — select event, agent, conditions, write definition file - [ ] Step 3: Edit an existing hook - [ ] Step 4: Remove a hook - [ ] Step 5: Sync hooks to tools ``` ## Step 0 — Detect Ambiguity (P8 B1) Before any action, scan the user's request and provided context for unresolved questions in scope, acceptance criteria, irreversibility, or constraint conflicts (contradictory inputs, missing target, unknown convention). 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. This is the default path, not an exception. Acceptable to proceed without asking ONLY when scope is single-target, single-concern, and the brief alone is testable. Any residual ambiguity discovered mid-workflow invokes the same protocol. ## Learnings Consultation If `.hatch3r/learnings/` exists, scan for learnings related to hook configurations, event trigger patterns, or prior hook issues before starting. ## Step 1: Discover Current State 1. Check `hooks/` for existing hook definition files (`.md` files with frontmatter). 2. Read `.hatch3r/hatch.json` for configured tools and features. 3. List existing hooks with their event, agent, and conditions. Present the current state: ``` Current Hooks: {list with id, event, agent ...