speckit-extension

Spec Kit — extensions

Manage spec-kit extensions with the Specify CLI specify extension command group. Extensions add reusable commands/hooks to a spec-kit project.

Prerequisite: needs the specify CLI. If specify --version fails, install it with the speckit-cli-setup skill first.

When to use

• Find, install, update, or remove a spec-kit extension.
• Temporarily enable/disable an extension or adjust its resolution priority.
• Add or manage extension catalog sources.

How to invoke

# Discover
specify extension list
specify extension list --json                 # machine-readable installed inventory (CLI >= 1.0.7)
specify extension search <query>
specify extension info <name>

# Install
specify extension add <name>
specify extension add <name> --force            # overwrite if already installed
specify extension add <path> --dev              # install from a local directory
specify extension add <name> --from <url>       # install from a custom URL
specify extension add <name> --priority <n>     # lower number = higher precedence

# Lifecycle
specify extension update [<name>]               # update one or all extensions
specify extension enable <name>
specify extension disable <name>
specify extension set-priority <name> <n>
specify extension remove <name>

# Catalogs (sources extensions are resolved from)
specify extension catalog list
specify extension catalog add <https-url> --name <name> [--install-allowed] [--priority <n>] [--description <text>]
specify extension catalog remove <name>

Extension catalog URLs must use HTTPS. New catalogs are not install-allowed by default — pass --install-allowed to permit installing extensions from them.

Notes

• Resolution priority: lower number = higher precedence (default 10).
• specify extension list --json requires Specify CLI >= 1.0.7 and returns installed extensions only, even when combined with --available or --all. Each item includes id, name, description, version, nullable author, priority, enabled, normalized source, and provides counts for commands, templates, scripts, and hooks.
• Prefer specify extension search first so you install the correct extension ID.
• --dev is for local development of an extension; point it at the extension's source directory.
• When the project was initialized in skills mode (see the speckit-init skill), an installed extension's commands land as .github/skills/speckit-<cmd>/SKILL.md. To make Copilot pick up the new skills in the current session, run /skills reload (no restart needed). They are also loaded automatically on the next session start.