fix(extensions): emit EXECUTE_COMMAND_INVOCATION in template hook examples

The dispatch-contract bullet tells the agent to self-dispatch using the
EXECUTE_COMMAND_INVOCATION line, but the mandatory-hook example blocks in
the templates (and the API-reference example) never emitted that line and
hardcoded `Executing: /{command}`. In skills-mode sessions /{command}
isn't a runnable form, so the instruction wasn't self-contained.

- All 9 templates (pre- and post-hook example blocks, 18 total): emit
  `EXECUTE_COMMAND_INVOCATION: {invocation}` and use {invocation} for the
  Executing line. Define {invocation} as the environment-correct command
  form (usually /{command}; skills mode renders /skill:speckit-* or
  $speckit-*) so the placeholder is self-explaining.
- EXTENSION-API-REFERENCE.md: mandatory-hook example now shows the
  INVOCATION line and explains {invocation}.
- Test: count emitted EXECUTE_COMMAND_INVOCATION directive lines (indented,
  inside the fence) and require one per EXECUTE_COMMAND block, so a prose
  mention can't mask a missing line and templates can't regress to
  emitting only EXECUTE_COMMAND.

Follow-up to #2730.

Author: Quratulain-bilal

extensions/EXTENSION-API-REFERENCE.md

@@ -631,10 +631,14 @@ Or for mandatory hooks:
 
 ```markdown
 **Automatic Hook**: {extension}
-Executing: `/{command}`
+Executing: `{invocation}`
 EXECUTE_COMMAND: {command}
+EXECUTE_COMMAND_INVOCATION: {invocation}
 ```
 
+Here `{invocation}` is the environment-correct command form: usually `/{command}`, but
+skills-mode sessions render it as e.g. `/skill:speckit-*` or `$speckit-*`.
+
 > **Dispatch contract**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI
 > orchestrators that watch agent output — emitting it does not execute anything by
 > itself. Because the agent cannot reliably tell whether such an orchestrator is

templates/commands/analyze.md

@@ -40,12 +40,14 @@ You **MUST** consider the user input before proceeding (if not empty).
     ## Extension Hooks
 
     **Automatic Pre-Hook**: {extension}
-    Executing: `/{command}`
+    Executing: `{invocation}`
     EXECUTE_COMMAND: {command}
+    EXECUTE_COMMAND_INVOCATION: {invocation}
 
     Wait for the result of the hook command before proceeding to the Goal.
     ```
-  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself, using the invocation shown on the `EXECUTE_COMMAND_INVOCATION:` line (which is the correct command form for this environment — skills mode may render it as `/skill:speckit-*` or `$speckit-*` rather than `/<command>`), and wait for its result before proceeding.
+  - Here `{invocation}` is the command form for the current environment: usually `/{command}`, but skills-mode sessions render it differently (e.g. `/skill:speckit-*` or `$speckit-*`). Use the same value for both the `Executing:` and `EXECUTE_COMMAND_INVOCATION:` lines.
+  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself using `{invocation}` (the value on the `EXECUTE_COMMAND_INVOCATION:` line) and wait for its result before proceeding.
 - If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently
 
 ## Goal
@@ -226,10 +228,12 @@ After reporting, check if `.specify/extensions.yml` exists in the project root.
     ## Extension Hooks
 
     **Automatic Hook**: {extension}
-    Executing: `/{command}`
+    Executing: `{invocation}`
     EXECUTE_COMMAND: {command}
+    EXECUTE_COMMAND_INVOCATION: {invocation}
     ```
-  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself, using the invocation shown on the `EXECUTE_COMMAND_INVOCATION:` line (which is the correct command form for this environment — skills mode may render it as `/skill:speckit-*` or `$speckit-*` rather than `/<command>`), and wait for its result before reporting completion.
+  - Here `{invocation}` is the command form for the current environment: usually `/{command}`, but skills-mode sessions render it differently (e.g. `/skill:speckit-*` or `$speckit-*`). Use the same value for both the `Executing:` and `EXECUTE_COMMAND_INVOCATION:` lines.
+  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself using `{invocation}` (the value on the `EXECUTE_COMMAND_INVOCATION:` line) and wait for its result before reporting completion.
 - If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently
 
 ## Operating Principles

templates/commands/checklist.md

@@ -61,12 +61,14 @@ You **MUST** consider the user input before proceeding (if not empty).
     ## Extension Hooks
 
     **Automatic Pre-Hook**: {extension}
-    Executing: `/{command}`
+    Executing: `{invocation}`
     EXECUTE_COMMAND: {command}
+    EXECUTE_COMMAND_INVOCATION: {invocation}
 
     Wait for the result of the hook command before proceeding to the Execution Steps.
     ```
-  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself, using the invocation shown on the `EXECUTE_COMMAND_INVOCATION:` line (which is the correct command form for this environment — skills mode may render it as `/skill:speckit-*` or `$speckit-*` rather than `/<command>`), and wait for its result before proceeding.
+  - Here `{invocation}` is the command form for the current environment: usually `/{command}`, but skills-mode sessions render it differently (e.g. `/skill:speckit-*` or `$speckit-*`). Use the same value for both the `Executing:` and `EXECUTE_COMMAND_INVOCATION:` lines.
+  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself using `{invocation}` (the value on the `EXECUTE_COMMAND_INVOCATION:` line) and wait for its result before proceeding.
 - If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently
 
 ## Execution Steps
@@ -361,8 +363,10 @@ Check if `.specify/extensions.yml` exists in the project root.
     ## Extension Hooks
 
     **Automatic Hook**: {extension}
-    Executing: `/{command}`
+    Executing: `{invocation}`
     EXECUTE_COMMAND: {command}
+    EXECUTE_COMMAND_INVOCATION: {invocation}
     ```
-  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself, using the invocation shown on the `EXECUTE_COMMAND_INVOCATION:` line (which is the correct command form for this environment — skills mode may render it as `/skill:speckit-*` or `$speckit-*` rather than `/<command>`), and wait for its result before reporting completion.
+  - Here `{invocation}` is the command form for the current environment: usually `/{command}`, but skills-mode sessions render it differently (e.g. `/skill:speckit-*` or `$speckit-*`). Use the same value for both the `Executing:` and `EXECUTE_COMMAND_INVOCATION:` lines.
+  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself using `{invocation}` (the value on the `EXECUTE_COMMAND_INVOCATION:` line) and wait for its result before reporting completion.
 - If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently

templates/commands/clarify.md

@@ -44,12 +44,14 @@ You **MUST** consider the user input before proceeding (if not empty).
     ## Extension Hooks
 
     **Automatic Pre-Hook**: {extension}
-    Executing: `/{command}`
+    Executing: `{invocation}`
     EXECUTE_COMMAND: {command}
+    EXECUTE_COMMAND_INVOCATION: {invocation}
 
     Wait for the result of the hook command before proceeding to the Outline.
     ```
-  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself, using the invocation shown on the `EXECUTE_COMMAND_INVOCATION:` line (which is the correct command form for this environment — skills mode may render it as `/skill:speckit-*` or `$speckit-*` rather than `/<command>`), and wait for its result before proceeding.
+  - Here `{invocation}` is the command form for the current environment: usually `/{command}`, but skills-mode sessions render it differently (e.g. `/skill:speckit-*` or `$speckit-*`). Use the same value for both the `Executing:` and `EXECUTE_COMMAND_INVOCATION:` lines.
+  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself using `{invocation}` (the value on the `EXECUTE_COMMAND_INVOCATION:` line) and wait for its result before proceeding.
 - If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently
 
 ## Outline
@@ -249,10 +251,12 @@ Check if `.specify/extensions.yml` exists in the project root.
     ## Extension Hooks
 
     **Automatic Hook**: {extension}
-    Executing: `/{command}`
+    Executing: `{invocation}`
     EXECUTE_COMMAND: {command}
+    EXECUTE_COMMAND_INVOCATION: {invocation}
     ```
-  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself, using the invocation shown on the `EXECUTE_COMMAND_INVOCATION:` line (which is the correct command form for this environment — skills mode may render it as `/skill:speckit-*` or `$speckit-*` rather than `/<command>`), and wait for its result before reporting completion.
+  - Here `{invocation}` is the command form for the current environment: usually `/{command}`, but skills-mode sessions render it differently (e.g. `/skill:speckit-*` or `$speckit-*`). Use the same value for both the `Executing:` and `EXECUTE_COMMAND_INVOCATION:` lines.
+  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself using `{invocation}` (the value on the `EXECUTE_COMMAND_INVOCATION:` line) and wait for its result before reporting completion.
   - **Optional hook** (`optional: true`):
     ```
     ## Extension Hooks

templates/commands/constitution.md

@@ -41,12 +41,14 @@ You **MUST** consider the user input before proceeding (if not empty).
     ## Extension Hooks
 
     **Automatic Pre-Hook**: {extension}
-    Executing: `/{command}`
+    Executing: `{invocation}`
     EXECUTE_COMMAND: {command}
+    EXECUTE_COMMAND_INVOCATION: {invocation}
 
     Wait for the result of the hook command before proceeding to the Outline.
     ```
-  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself, using the invocation shown on the `EXECUTE_COMMAND_INVOCATION:` line (which is the correct command form for this environment — skills mode may render it as `/skill:speckit-*` or `$speckit-*` rather than `/<command>`), and wait for its result before proceeding.
+  - Here `{invocation}` is the command form for the current environment: usually `/{command}`, but skills-mode sessions render it differently (e.g. `/skill:speckit-*` or `$speckit-*`). Use the same value for both the `Executing:` and `EXECUTE_COMMAND_INVOCATION:` lines.
+  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself using `{invocation}` (the value on the `EXECUTE_COMMAND_INVOCATION:` line) and wait for its result before proceeding.
 - If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently
 
 ## Outline
@@ -145,8 +147,10 @@ Check if `.specify/extensions.yml` exists in the project root.
     ## Extension Hooks
 
     **Automatic Hook**: {extension}
-    Executing: `/{command}`
+    Executing: `{invocation}`
     EXECUTE_COMMAND: {command}
+    EXECUTE_COMMAND_INVOCATION: {invocation}
     ```
-  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself, using the invocation shown on the `EXECUTE_COMMAND_INVOCATION:` line (which is the correct command form for this environment — skills mode may render it as `/skill:speckit-*` or `$speckit-*` rather than `/<command>`), and wait for its result before reporting completion.
+  - Here `{invocation}` is the command form for the current environment: usually `/{command}`, but skills-mode sessions render it differently (e.g. `/skill:speckit-*` or `$speckit-*`). Use the same value for both the `Executing:` and `EXECUTE_COMMAND_INVOCATION:` lines.
+  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself using `{invocation}` (the value on the `EXECUTE_COMMAND_INVOCATION:` line) and wait for its result before reporting completion.
 - If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently

templates/commands/implement.md

@@ -40,12 +40,14 @@ You **MUST** consider the user input before proceeding (if not empty).
     ## Extension Hooks
 
     **Automatic Pre-Hook**: {extension}
-    Executing: `/{command}`
+    Executing: `{invocation}`
     EXECUTE_COMMAND: {command}
+    EXECUTE_COMMAND_INVOCATION: {invocation}
     
     Wait for the result of the hook command before proceeding to the Outline.
     ```
-  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself, using the invocation shown on the `EXECUTE_COMMAND_INVOCATION:` line (which is the correct command form for this environment — skills mode may render it as `/skill:speckit-*` or `$speckit-*` rather than `/<command>`), and wait for its result before proceeding.
+  - Here `{invocation}` is the command form for the current environment: usually `/{command}`, but skills-mode sessions render it differently (e.g. `/skill:speckit-*` or `$speckit-*`). Use the same value for both the `Executing:` and `EXECUTE_COMMAND_INVOCATION:` lines.
+  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself using `{invocation}` (the value on the `EXECUTE_COMMAND_INVOCATION:` line) and wait for its result before proceeding.
 - If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently
 
 ## Outline
@@ -190,10 +192,12 @@ Check if `.specify/extensions.yml` exists in the project root.
     ## Extension Hooks
 
     **Automatic Hook**: {extension}
-    Executing: `/{command}`
+    Executing: `{invocation}`
     EXECUTE_COMMAND: {command}
+    EXECUTE_COMMAND_INVOCATION: {invocation}
     ```
-  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself, using the invocation shown on the `EXECUTE_COMMAND_INVOCATION:` line (which is the correct command form for this environment — skills mode may render it as `/skill:speckit-*` or `$speckit-*` rather than `/<command>`), and wait for its result before reporting completion.
+  - Here `{invocation}` is the command form for the current environment: usually `/{command}`, but skills-mode sessions render it differently (e.g. `/skill:speckit-*` or `$speckit-*`). Use the same value for both the `Executing:` and `EXECUTE_COMMAND_INVOCATION:` lines.
+  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself using `{invocation}` (the value on the `EXECUTE_COMMAND_INVOCATION:` line) and wait for its result before reporting completion.
   - **Optional hook** (`optional: true`):
     ```
     ## Extension Hooks

templates/commands/plan.md

@@ -48,12 +48,14 @@ You **MUST** consider the user input before proceeding (if not empty).
     ## Extension Hooks
 
     **Automatic Pre-Hook**: {extension}
-    Executing: `/{command}`
+    Executing: `{invocation}`
     EXECUTE_COMMAND: {command}
+    EXECUTE_COMMAND_INVOCATION: {invocation}
 
     Wait for the result of the hook command before proceeding to the Outline.
     ```
-  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself, using the invocation shown on the `EXECUTE_COMMAND_INVOCATION:` line (which is the correct command form for this environment — skills mode may render it as `/skill:speckit-*` or `$speckit-*` rather than `/<command>`), and wait for its result before proceeding.
+  - Here `{invocation}` is the command form for the current environment: usually `/{command}`, but skills-mode sessions render it differently (e.g. `/skill:speckit-*` or `$speckit-*`). Use the same value for both the `Executing:` and `EXECUTE_COMMAND_INVOCATION:` lines.
+  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself using `{invocation}` (the value on the `EXECUTE_COMMAND_INVOCATION:` line) and wait for its result before proceeding.
 - If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently
 
 ## Outline
@@ -89,10 +91,12 @@ Check if `.specify/extensions.yml` exists in the project root.
     ## Extension Hooks
 
     **Automatic Hook**: {extension}
-    Executing: `/{command}`
+    Executing: `{invocation}`
     EXECUTE_COMMAND: {command}
+    EXECUTE_COMMAND_INVOCATION: {invocation}
     ```
-  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself, using the invocation shown on the `EXECUTE_COMMAND_INVOCATION:` line (which is the correct command form for this environment — skills mode may render it as `/skill:speckit-*` or `$speckit-*` rather than `/<command>`), and wait for its result before reporting completion.
+  - Here `{invocation}` is the command form for the current environment: usually `/{command}`, but skills-mode sessions render it differently (e.g. `/skill:speckit-*` or `$speckit-*`). Use the same value for both the `Executing:` and `EXECUTE_COMMAND_INVOCATION:` lines.
+  - **Dispatch contract for mandatory hooks**: the `EXECUTE_COMMAND:` line is only a dispatch signal for CLI orchestrators that watch agent output — emitting it does not run anything. You MUST then invoke the hook yourself using `{invocation}` (the value on the `EXECUTE_COMMAND_INVOCATION:` line) and wait for its result before reporting completion.
   - **Optional hook** (`optional: true`):
     ```
     ## Extension Hooks