hatch3r-handoff-prepare

# Handoff Preparation ## Quick Start ``` Task Progress: - [ ] Step 0: Detect ambiguity (P8 B1) - [ ] Step 1: Gather session state (git_ref, files, tests, work_item) - [ ] Step 2: Compose body (8 required sections + user-tier markers) - [ ] Step 3: Validate against readiness rule - [ ] Step 4: Write to .hatch3r/handoffs/active/<id>.md (through the capture gate when available) - [ ] Step 5: Confirm with path, summary, and Iteration Summary ``` ## 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: target_agent (named vs `any`), status (`in-progress` vs `open` vs `handed-off`), overwrite policy when a same-`work_item` handoff exists (<24h vs supersede), expected resumer scope, and whether secret-redaction is needed in the body. ## 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: Gather State Collect the inputs required by the handoff schema (see `.hatch3r/handoffs/README.md` for the canonical schema): ...