What problem does it solve? When an engineering request in the MDE AI repository is ambiguous or spans multiple domains, it is unclear which skill or workflow should own the work. This Skill resolves that ambiguity by routing each non-trivial request to exactly one canonical execution owner while enforcing independent verification for high-risk S4 changes. ## Core Features & Use Cases - Single-owner routing: Chooses exactly one owner from canonical workflow skills (tasks, systematic-debugging, research, code-review, task-verifier) or domain/vendor skills (copilotkit, mastra, supabase, gemini, stripe) and stops. - S4 safety enforcement: Flags payments, auth/RLS/tenant-boundary, secrets, and irreversible production changes as S4, requiring independent verification by task-verifier instead of self-certification. - Contract-tested routing: Ships a Python test script and 15 eval cases that validate routing rules, retired-owner rejection, and S4 verifier requirements. - Use Case: A request like "Change Supabase RLS tenant access rules" is routed to the supabase skill, marked S4, and blocked from completion until task-verifier independently confirms the work. ## Quick Start Ask the assistant to route an ambiguous MDE engineering request, such as determining which skill should own an unclear cross-repo implementation task.
