ros/spec-kit
1
0
Fork 0
mirror of https://github.com/github/spec-kit.git synced 2026-04-01 10:13:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

feat: add superpowers bridge extension to community catalog (#2023)

Browse Source 
* docs: correct specify extension add syntax to require extension name

The specify extension add command requires the extension name as a positional argument. Many documentation files incorrectly demonstrated using the --from flag without specifying the extension name first.

* feat: add superb extension to community catalog

Orchestrates obra/superpowers skills within the spec-kit SDD workflow.

* fix: link superb extension docs
This commit is contained in:
Hamilton Snow
2026-03-31 19:25:11 +08:00
committed by GitHub
parent 9cb3f3d1ad
commit b19a7eedfa
7 changed files with 62 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
extensions/EXTENSION-USER-GUIDE.md
View File

@@ -160,7 +160,7 @@ This will:
```bash
# From GitHub release
specify extension add --from https://github.com/org/spec-kit-ext/archive/refs/tags/v1.0.0.zip
specify extension add <extension-name> --from https://github.com/org/spec-kit-ext/archive/refs/tags/v1.0.0.zip
```
### Install from Local Directory (Development)
@@ -737,7 +737,7 @@ You can still install extensions not in your catalog using `--from`:
specify extension add jira
# Direct URL (bypasses catalog)
specify extension add --from https://github.com/someone/spec-kit-ext/archive/v1.0.0.zip
specify extension add <extension-name> --from https://github.com/someone/spec-kit-ext/archive/v1.0.0.zip
# Local development
specify extension add --dev /path/to/extension
@@ -807,7 +807,7 @@ specify extension add --dev /path/to/extension
2. Install older version of extension:
```bash
specify extension add --from https://github.com/org/ext/archive/v1.0.0.zip
specify extension add <extension-name> --from https://github.com/org/ext/archive/v1.0.0.zip
```
### MCP Tool Not Available