Mandatory Trigger Gate

Before ordinary intent or skill routing, scan the user request for the literal trigger: token.
When present, resolve and load the exact matching shortcut before invoking any dependency or semantically related skill.
When a shortcut matches, announce Using [shortcut name].
Treat the shortcut as the end-to-end contract. A wrapped skill's success does not complete the shortcut while later shortcut steps remain.
If the user later questions a trigger's outcome, re-read the matched shortcut and compare every required action before explaining or correcting the result.
When absent, do not invoke shortcuts.

Context

Shortcuts are a small self-contained workflow that can be triggered via trigger:<shortcut-name>, for example trigger:merge-pr.

ALWAYS use the shortcut when user mentions trigger:<shortcut>. Read the shortcut file and follow literally.

Shortcuts can be in the following locations: