fix(integrations): dispatch kiro-cli headless and install hyphenated prompts

.devcontainer/post-create.sh

@@ -75,17 +75,12 @@ run_command "echo \"$KIRO_INSTALLER_SHA256  $KIRO_INSTALLER_PATH\" | sha256sum -
 
 run_command "bash \"$KIRO_INSTALLER_PATH\""
 
-kiro_binary=""
-if command -v kiro-cli >/dev/null 2>&1; then
-  kiro_binary="kiro-cli"
-elif command -v kiro >/dev/null 2>&1; then
-  kiro_binary="kiro"
-else
-  echo -e "\033[0;31m[ERROR] Kiro CLI installation did not create 'kiro-cli' or 'kiro' in PATH.\033[0m" >&2
+if ! command -v kiro-cli >/dev/null 2>&1; then
+  echo -e "\033[0;31m[ERROR] Kiro CLI installation did not create 'kiro-cli' in PATH.\033[0m" >&2
   exit 1
 fi
 
-run_command "$kiro_binary --help > /dev/null"
+run_command "kiro-cli --help > /dev/null"
 echo "✅ Done"
 
 echo -e "\n🤖 Installing Kimi Code CLI..."

docs/reference/extensions.md

@@ -32,6 +32,8 @@ specify extension add <name>
 
 Installs an extension from the catalog, a URL, or a local directory. Extension commands are registered with the active AI coding agent integration. For `generic`, invocations use the configured `--commands-dir`: flat command files by default, or `speckit-<name>/SKILL.md` with `--skills`. The core `speckit.taskstoissues` command remains available alongside the GitHub extension's namespaced replacement during migration.
 
+Installation is refused when a command or alias would write the same file as a core command or another installed extension's command once dots become hyphens, as Cline, Forge, Junie, Kiro CLI and skills-based integrations name their files (for example `speckit.foo.bar-baz` and `speckit.foo-bar.baz`). An extension installed before this check that shares such a file is not registered for Kiro CLI or Qoder CLI, and keeps its existing files, until it is updated or removed, or the extension it shares the file with is removed.
+
 If a generic integration refresh cannot produce every extension invocation (for example, because a command or skill is user-modified or its source is missing), it warns and restores that extension's prior registered artifacts. Other extensions can still refresh.
 
 An unqualified catalog install still selects the advertised current version.
@@ -56,6 +58,11 @@ specify extension remove <name>
 
 Removes an installed extension. Configuration files are backed up by default; use `--keep-config` to leave them in place or `--force` to skip the confirmation.
 
+For older Kiro CLI or Qoder CLI extensions whose names collide after hyphenation,
+removal deletes the extension's legacy commands but preserves a shared migrated
+prompt or skill unless its source marker identifies the removed extension as
+the owner. Installed core commands are also preserved.
+
 ## List Installed Extensions
 
 ```bash

docs/reference/integrations.md

@@ -31,7 +31,7 @@ The Specify CLI supports a wide range of AI coding agents. When you run `specify
 | [Junie](https://junie.jetbrains.com/)                                                | `junie`          |                                                                                                                                           |
 | [Kilo Code](https://github.com/Kilo-Org/kilocode)                                    | `kilocode`       | Installs commands into `.kilo/commands`; legacy `.kilocode/workflows` installs remain supported as a registration fallback                 |
 | [Kimi Code](https://code.kimi.com/)                                                  | `kimi`           | Skills-based integration; installs into `.kimi-code/skills/`. `--migrate-legacy` moves old `.kimi/skills/` installs to the new paths |
-| [Kiro CLI](https://kiro.dev/docs/cli/)                                               | `kiro-cli`       | Kiro CLI does not substitute `$ARGUMENTS` in file-based prompts, so Spec Kit ships a prose fallback at render time (see [Manage prompts](https://kiro.dev/docs/cli/chat/manage-prompts/) and issue [#1926](https://github.com/github/spec-kit/issues/1926)). Alias: `--integration kiro` |
+| [Kiro CLI](https://kiro.dev/docs/cli/)                                               | `kiro-cli`       | Installs prompts as `.kiro/prompts/speckit-<command>.md` and invokes them as `/speckit-<command>`, because Kiro CLI does not run slash commands whose names contain dots. Headless workflow dispatch runs `kiro-cli chat --no-interactive --trust-all-tools`, which auto-approves every tool call: without it, Kiro denies all file writes in non-interactive mode and still exits 0. Spec Kit looks for the `kiro-cli` executable only, because a bare `kiro` launches Kiro IDE by default. Kiro CLI does not substitute `$ARGUMENTS` in file-based prompts, so Spec Kit ships a prose fallback at render time (see [Manage prompts](https://kiro.dev/docs/cli/chat/manage-prompts/) and issue [#1926](https://github.com/github/spec-kit/issues/1926)). `specify integration upgrade kiro-cli` renames existing prompts, and refuses before changing files while presets have commands registered for Kiro CLI, or while an extension alias such as `speckit-plan` (accepted by Spec Kit 1.0.7 and earlier) already has its own prompt where a core prompt goes. An extension installed before Spec Kit rejected names that hyphenate to an existing prompt is not registered for Kiro CLI and keeps its existing prompts: two extensions with `speckit.foo.bar-baz` and `speckit.foo-bar.baz` stay that way until one is removed, and one with an alias such as `plan` until it is updated or removed. |
 | [Lingma](https://lingma.aliyun.com/)                                                 | `lingma`         | Skills-based integration; skills are installed automatically                                                                               |
 | [MiniMax Code](https://github.com/MiniMax-AI/minimax-code)                          | `mcode`          | Skills-based integration; installs skills into `.minimax/skills` and invokes them as `/speckit-<command>`. Headless workflow dispatch uses `--permission full` so tool actions are not blocked by headless permission gating; set `SPECKIT_INTEGRATION_MCODE_EXTRA_ARGS="--permission smart"` to use MiniMax Code's stricter policy. |
 | [Mistral Vibe](https://github.com/mistralai/mistral-vibe)                            | `vibe`           |                                                                                                                                           |

src/specify_cli/_utils.py

@@ -170,11 +170,7 @@ def check_tool(tool: str, tracker=None) -> bool:
             return True
 
     # Per-integration executable resolution.
-    if tool == "kiro-cli":
-        # Kiro currently supports both executable names. Prefer kiro-cli and
-        # accept kiro as a compatibility fallback.
-        found = shutil.which("kiro-cli") is not None or shutil.which("kiro") is not None
-    elif tool == "rovodev":
+    if tool == "rovodev":
         found = shutil.which("acli") is not None
     elif tool == "docker-agent":
         found = docker_agent_command() is not None

src/specify_cli/agents.py

@@ -1352,7 +1352,10 @@ def register_commands_for_non_skill_agents(
         return results
 
     def unregister_commands(
-        self, registered_commands: Dict[str, List[str]], project_root: Path
+        self,
+        registered_commands: Dict[str, List[str]],
+        project_root: Path,
+        preserved_output_names: Dict[str, set[str]] | None = None,
     ) -> None:
         """Remove previously registered command files from agent directories.
 
@@ -1361,9 +1364,15 @@ def unregister_commands(
         commands left behind after an ``integration upgrade`` are
         cleaned up as well.
 
+        ``preserved_output_names`` maps an agent to formatted stems that
+        must stay. Extension removal protects installed core commands and
+        shared migrated files not owned by the extension being removed.
+        Protection applies to both formatted and raw command names.
+
         Args:
             registered_commands: Dict mapping agent names to command name lists
             project_root: Path to project root
+            preserved_output_names: Agent -> formatted stems to leave in place
         """
         self._ensure_configs()
         for agent_name, cmd_names in registered_commands.items():
@@ -1384,13 +1393,24 @@ def unregister_commands(
                 if legacy_dir.exists() and legacy_dir != commands_dir:
                     dirs_to_clean.append(legacy_dir)
 
+            preserved = {
+                os.path.normcase(name)
+                for name in (preserved_output_names or {}).get(agent_name, ())
+                if isinstance(name, str)
+            }
             for cmd_name in cmd_names:
                 output_name = self._compute_output_name(
                     agent_name, cmd_name, agent_config
                 )
 
-                names_to_clean = [output_name]
-                if output_name != cmd_name and self._is_safe_command_name(cmd_name):
+                names_to_clean = []
+                if os.path.normcase(output_name) not in preserved:
+                    names_to_clean.append(output_name)
+                if (
+                    output_name != cmd_name
+                    and os.path.normcase(cmd_name) not in preserved
+                    and self._is_safe_command_name(cmd_name)
+                ):
                     names_to_clean.append(cmd_name)
 
                 for target_dir in dirs_to_clean: