What problem does it solve? When several externally-installed global skills all auto-trigger on the same technology domain (e.g. Android/Kotlin/Compose), they produce contradictory guidance, fire in the wrong order, or crowd out the correct specialist. This Skill replaces fuzzy auto-trigger with deterministic precedence, ordering, and an explicit tie-break reason for every overlap. ## Core Features & Use Cases - Precedence contract: Defines a four-part contract every domain overlay must provide — detection signals, a precedence table with tie-break reasons, lane-step mapping, and a pre-review audit gate. - Reusable precedence heuristics: Supplies decision rules (sole authority, authoring vs measurement, fact-checker role, recency, scope guard) for picking a winner between overlapping skills. - Engineer integration: Hooks into the engineer workflow's construct/test/verify steps so the matching <domain>-advisor decides which specialist fills each existing lane step. - Use Case: A team with four overlapping Compose skills installed creates an android-advisor overlay so that writing a screen deterministically routes to one state-management skill, sequences the perf audit after authoring, and runs a domain self-audit before review. ## Quick Start Ask the agent to apply the domain-overlay pattern to create an advisor for your technology domain that picks a winning skill per sub-task with a stated reason.
