hatch3r-architecture-review

# Architecture Review Workflow ## Quick Start ``` Task Progress: - [ ] Step 0: Detect ambiguity (P8 B1) - [ ] Step 1: Read existing ADRs and the template - [ ] Step 2: Define the decision context — problem, constraints, options - [ ] Step 3: Evaluate options — pros/cons, prototype if needed, check ADR constraints - [ ] Step 4: For external library docs and current best practices, follow the project's tooling hierarchy - [ ] Step 5: Write ADR following the template - [ ] Step 6: Update affected specs or docs to reference the new ADR ``` ## 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: problem framing (what decision needs to be made), constraint set (mandatory vs preferred), evaluation horizon (short-term vs long-term cost), supersedes which prior ADR, and ADR status target (PROPOSED for discussion vs ACCEPTED for binding decision). ## Fan-out Discipline (P8 B2) Fan-out scales with task size; token cost never justifies serializing independent work (`rules/hatch3r-fan-out-discipline.md` P8 B2; `agents/shared/efficiency-patterns.md`). Emit `sub_agents_spawned: { count, rationale, task_structure }` in your output. ## Step 1: Read Existing...