All notable changes to the Superpowers Bridge extension will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- v1.0.1 could not be installed via
specify extension add superspec. The catalog downloads GitHub's generated tag ZIP, and spec-kit validates it before extracting (_download_security.py: 10 MiB per member, 50 MiB total, 512 entries).assets/workflow-overview-en.pngis ~12 MiB, so the install aborted withZIP member ... exceeds maximum size of 10485760 bytes(issue #6). The archive now ships only the runtime payload: 0.04 MiB downloaded, 25 entries, largest member 0.02 MiB.
.gitattributesmarks documentation media (assets/), samples (examples/), development tooling (scripts/) and CI (.github/) asexport-ignore, sogit archive— and therefore GitHub's tag ZIP — omits them. The repository, the rendered README images and--devinstalls are unchanged; nothing was deleted or recompressed.- Documentation now uses spec-kit's real
specs/NNN-*/feature layout instead of.specify/specs/.
scripts/validate-release-archive.pyrebuilds the published archive and fails CI when it approaches any spec-kit install limit, loses a fileextension.ymldeclares, or regains an export-ignored path.- Structural and AI-driven end-to-end tests (
scripts/e2e-smoke.sh,scripts/e2e-agent-claude.sh) verify a real spec-kit install.
- Catalog namespace alignment (BREAKING for command names):
extension.idrenamed fromsuperpowerstosuperspec(matches repository name and the catalog id required by spec-kit's registry validator).- All command names migrated:
/speckit.superpowers.{status,brainstorm,tasks,execute,review}→/speckit.superspec.{status,brainstorm,tasks,execute,review}. - All three lifecycle hooks (
after_tasks,before_implement,after_implement) now point to the newspeckit.superspec.*commands. - README catalog install command updated to
specify extension add superspec.
- v1.0.0 could not be installed via
specify extension add superpowers-bridgedue to a mismatch between the catalog id and the command namespace (Validation Error: Command 'speckit.superpowers.status' must use extension namespace 'superpowers-bridge'). v1.0.1 fixes this by aligning the namespace with the (renamed) catalog id.
scripts/validate-extension-metadata.pyrewritten to derive the expected namespace dynamically fromextension.yml'sid, so future namespace/slug drift fails CI before reaching the catalog. New checks:- every
commands[].nameand everyhooks[].commandmust start withspeckit.<extension.id>.; - the README catalog install command's slug must equal
extension.id; - docs must not retain legacy
speckit.superpowers.*references.
- every
- Extension manifest (
extension.yml) for spec-kit extension registry - 5 superpowers-bridge commands: status, brainstorm, tasks, execute, review
- 3 lifecycle hooks: after-tasks, before-execute, after-execute
- 5 enhanced templates: constitution, spec, plan, tasks, checklist
- Session resumability via
progress.ymlandsuperpowers.yml - Superpowers detection with graceful fallback when skills not installed
- Built-in brainstorming protocol (5 categories) as fallback for superpowers
- Built-in code review checklist as fallback for requesting-code-review
- TDD/REVIEW/SUBAGENT execution markers in task templates
- Bilingual documentation (English + Chinese)
- Architecture diagrams for both EN and CN
- Reference documentation: workflow guide and superpowers bridge
- End-to-end sample workflow example