Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From speckit-dev
Install, list, enable/disable, update, and configure GitHub spec-kit extensions, and manage the catalog stack. Use when running `specify extension` commands, wiring a team/internal catalog, resolving the PyPI specify-cli install footgun, configuring .specify/extension-catalogs.yml or extensions.yml, or when the user runs /speckit-dev:manage.
How this skill is triggered — by the user, by Claude, or both
Slash command
/speckit-dev:manage What to manage? (e.g. 'install jira from our team catalog', 'add an internal catalog')What to manage? (e.g. 'install jira from our team catalog', 'add an internal catalog')The summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Verify-canonical guard.** CLI flags/behavior are pinned to v0.12.x
Verify-canonical guard. CLI flags/behavior are pinned to v0.12.x (2026-07-04). Confirm against
references/cli-and-catalogs.rstand the live extensions reference and user guide.
uv tool install specify-cli --from git+https://github.com/github/spec-kit.git
Plain pip install specify-cli from PyPI is an unrelated stub without the
extension/preset commands.
| Command | Purpose | Key flags |
|---|---|---|
specify extension search [q] | search catalogs | --tag --author --verified |
specify extension add <name> | install | --dev <path>, --from <url>, --force, --priority N |
specify extension remove <name> | uninstall | --keep-config, --force |
specify extension list | installed | --available, --all |
specify extension info <name> | details | |
specify extension update [name] | update one/all | |
specify extension enable/disable <name> | toggle | |
specify extension set-priority <name> <N> | resolution order | |
specify extension catalog list/add/remove | manage catalogs | add: --name --priority --install-allowed |
SPECKIT_CATALOG_URL env → project .specify/extension-catalogs.yml → user
~/.specify/extension-catalogs.yml → built-in defaults (official +
community). Lower priority number wins on id conflicts. See
assets/extension-catalogs.yml for wiring a team catalog with
install_allowed: true.
extension defaults → <ext>-config.yml → <ext>-config.local.yml →
SPECKIT_<EXT>_* env.
Commit .specify/extensions.yml + <ext>-config.yml. Gitignore
.specify/extensions/.cache/, .backup/, *.local.yml, .registry.
See references/cli-and-catalogs.rst and references/canonical-sources.rst.
npx claudepluginhub nq-rdl/agent-extensions --plugin speckit-devGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.