What problem does it solve? When a runtime smoke probe fails on a flow contract you do not own, builder agents need a deterministic response path: fix their own implementation or escalate to the lead, without ever editing protected flow files. ## Core Features & Use Cases - Decision tree for probe failures: Maps FLOW_STEP_FAILED, FLOW_NEW_ENDPOINT_UNCOVERED, FLOW_OWNERSHIP_VIOLATION, FLOW_MERGE_CONFLICT, FLOW_DUPLICATE_ID, and FLOW_FILE_MISSING_OWNS_OR_EXTENDS diagnostics to the correct action. - Option A code-fix workflow: Guides reading the failing flow's expected status, body shape, side-effects, and capture bindings, then fixing the controller, service, or DTO and re-running pnpm probe:smoke. - Option B lead escalation: Provides ready-to-send ov mail flow_mismatch templates with probe output, spec citations, and proposed flow changes, plus handling of the worker-done pre-close gate. - Use Case: A builder's commit is blocked by FLOW_NEW_ENDPOINT_UNCOVERED after adding an endpoint; the skill directs them to mail the lead with the endpoint shape instead of editing the flow file. ## Quick Start When pnpm probe:smoke reports a FLOW_STEP_FAILED or FLOW_NEW_ENDPOINT_UNCOVERED error, invoke this skill to decide whether to fix my code or mail the lead.
