What problem does it solve? Engineering teams using AI-assisted delivery often apply the wrong level of process: heavyweight review ceremonies for trivial CSS tweaks, or lightweight direct edits on payment flows and state machines. This Skill prevents lane drift by giving any agent a deterministic 4-gate heuristic that selects the correct delivery lane (Direct, Kickoff, Deliberation Moderator, or Harness Runtime Controller) before implementation begins. ## Core Features & Use Cases - 4-Gate Lane Heuristic: Ordered gates route tasks to HRC (auth, payments, matching, state machines, DB migrations, WebSocket infra), DM (cross-workspace UX/architecture trade-offs), Kickoff (ambiguous scope), or Direct (bounded single-boundary changes). - Quick-Reference Matrix & Anti-Patterns: A concern-to-lane lookup table plus documented anti-patterns (e.g., HRC for a CSS tweak, Direct delivery for a payment flow) with corrective guidance. - Icebreaker Layer Map: A domain-specific mapping of icebreaker stack layers (session lifecycle, phase logic, AI copy, REST routes, UI, WebSocket) to their required lanes. - Use Case: Before modifying the icebreaker phase state machine, run the heuristic: Gate 1 matches on state-machine changes with partial-failure risk, so the task routes to Harness Runtime Controller with a Sprint Contract and verification gate instead of a direct edit. ## Quick Start Ask the agent to run the lane selection heuristic on your planned change, for example: which lane should I use for adding a refund endpoint to the payments service?
