[Extension]: Update speckit-superpowers-bridge to v1.3.0
I maintainer di solito rispondono entro 2 giorni
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Idoneità per principianti
- 68/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- bash, powershell
- Ambito
- tooling
Direzione di ricerca
Trova la voce esistente speckit-superpowers-bridge nel catalogo delle estensioni e confrontala con il JSON del catalogo proposto. Verifica la versione, l’URL di download immutabile, i metadati, il numero di comandi e hook e i requisiti, quindi esegui la convalida del catalogo o i test pertinenti; il lavoro è completato quando la voce v1.3.0 viene accettata senza errori di convalida.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Extension Submission: Superpowers Implementation Bridge
Update to existing community catalog entry speckit-superpowers-bridge.
Extension ID
speckit-superpowers-bridge
Extension Name
Superpowers Implementation Bridge
Version
1.3.0
Description
Thin orchestrator between Spec Kit design artifacts and Superpowers implementation discipline. Cross-agent; verified for Codex and Claude Code.
Author
lihan3238
Repository URL
https://github.com/lihan3238/speckit-superpowers-bridge
Download URL
The source repository's marketplace metadata keeps the stable latest-release alias for convenience. The official Spec Kit catalog submission uses this immutable versioned ZIP URL, as required for reproducible catalog installs.
License
MIT
Homepage
https://github.com/lihan3238/speckit-superpowers-bridge
Documentation URL
https://github.com/lihan3238/speckit-superpowers-bridge#readme
Changelog URL
https://github.com/lihan3238/speckit-superpowers-bridge/blob/main/CHANGELOG.md
Required Spec Kit Version
=0.8.10
Verified release baseline for v1.3.0:
- Spec Kit
1.0.12for repository bootstrap, Linux bash verification, and the v1.3.0 release sandbox; bridge runtime floor remains>=0.8.10. - Superpowers
6.4.2. - Codex CLI
0.157.1. - Claude Code
2.1.283.
Required Tools
- PowerShell
>=5.1for the Windows runtime flavor. - Bash
>=4.0andjq >=1.6for the Linux/macOS bash runtime flavor. - Superpowers skills in the active agent runtime when users want Superpowers implementation discipline.
- Codex or Claude Code integration generated by Spec Kit.
Number of Commands
3
Number of Hooks
5
Tags
bridge, superpowers, cross-agent, tdd, workflow
Key Features
-
Keeps Spec Kit as the design source of truth: constitution, spec, clarify, plan, tasks, checklists, and analysis stay Spec Kit-owned.
-
Uses Superpowers as the implementation discipline: executing-plans, TDD, systematic debugging, review, verification, and branch finishing stay native Superpowers capabilities.
-
Adds a thin handoff/guard layer so the two systems do not duplicate planning or execution ownership.
-
Ships both bash and Windows PowerShell script flavors in one ZIP.
-
Supports Codex and Claude Code through the same handoff contract.
-
New in v1.0.0: release readiness checks for version, catalog id, command namespace, hook namespace, package contents, workflow inventory, platform rows, agent rows, and evidence completeness.
-
New in v1.0.0:
bridge-status --readiness/bridge-status.ps1 -Readinessread-only install health report covering script flavor, required tools, namespace, package files, bridge state, verified agent metadata, and next action. -
New in v1.0.3: re-verified end-to-end on Spec Kit CLI
0.10.2(Linux bash); declares the new first-classcategory: process/effect: read-writemanifest fields introduced by Spec Kit 0.10.2, backward compatible with the>=0.8.10runtime floor. -
New in v1.0.3: bootstrap documentation aligned with Spec Kit 0.10.0 init changes (git extension now opt-in, legacy
--ai*flags removed,branch_numbering→feature_numbering). -
New in v1.1.0: verified-against-Superpowers baseline moved
5.1.0→6.0.0(a major upstream bump) with zero bridge runtime change. Superpowers 6.0.0's breaking changes are all internal to upstream skills (subagent-driven-developmentreviewer-prompt consolidation, worktrees relocating to project.worktrees/, vendor-neutral prose, three new harnesses) and transparent to the thin bridge, which invokes Superpowers by skill name only. -
New in v1.2.0: audited and refreshed repository bootstrap against Spec Kit 0.16.4, including current templates, managed local-state ignore policy, and bundled git/agent-context sources; runtime floor remains
>=0.8.10. -
New in v1.2.0: verified-against-Superpowers baseline moved
6.0.0→6.3.0after all six invoked skill names and the Spec Kittasks.mdconsumption boundary were re-audited. -
New in v1.2.0: plug-and-play
before_implement/after_implementextension-hook dispatch from PR #14, hardened to Spec Kit 0.16.4 semantics. Mandatory hooks emitEXECUTE_COMMAND:, are actually invoked and awaited, and mandatory post-hooks finish before handoff completion; bridge-owned hooks remain skipped. -
New in v1.2.0: fixed Issue #13 by removing GNU-only
realpath -mfrom the bash handoff writer. Portable, symlink-aware missing-path normalization now works on standard macOS without GNU coreutils. -
New in v1.3.0: aligned tracked bootstrap sources and templates with Spec Kit 1.0.12, including current git/agent-context sources, command placeholders, and project gate preservation.
-
New in v1.3.0: advanced the verified-against-Superpowers baseline to 6.4.2 and documented inline
executing-planssemantics. -
New in v1.3.0: added a stable disposable adapter mapping Spec Kit checkbox tasks to the
Task Nheadings required by Superpowers 6.4.2, while keepingtasks.mdas the sole requirements source. -
New in v1.3.0: updated malformed
.specify/extensions.ymlhandling to report parser errors and state that no hooks, including mandatory hooks, were checked.
Support Matrix
| Target | Result | Evidence |
|---|---|---|
| Linux bash | PASS | bash tests/run-all.sh (9/9) on Spec Kit 1.0.12, source/package validators, and the public-v1.3.0 WSL2 sandbox cycle. |
| Windows PowerShell 5.1+ | PASS | Native tests/test-release-powershell.ps1, readiness validation, and the public-v1.3.0 Windows sibling sandbox cycle (v1-3-0-windows-20260926T111613Z). |
| macOS bash | PASS | GitHub-hosted native macOS release gate runs the full bash suite and the Issue #13 portability regression; no local public-artifact sandbox claim. |
| Codex | PASS | v1.3.0 implementation, source verification, and public-artifact cycle with Codex CLI 0.157.1. |
| Claude Code | PASS | Claude Code 2.1.283 integration/skill contract verification recorded in the v1.3.0 feature evidence; the official Claude marketplace currently serves Superpowers 6.4.1, while the upstream 6.4.2 source audit passes. |
Release Validation Summary
scripts/release/validate-release-readiness.ps1 -Version 1.3.0 -PackageZip dist/speckit-superpowers-bridge-v1.3.0.zippasses.scripts/release/test-validate-release-readiness.ps1passes, including negative fixtures for namespace drift, stale marketplace metadata, missing package flavor, missing agent rows, missing platform rows, and missing workflow evidence.bash tests/run-all.shpasses.tests/test-release-powershell.ps1passes under Windows PowerShell.- The macOS-hosted release gate passes the full bash suite and focused handoff portability regression.
- GitHub release asset API reports both ZIPs at 83,891 bytes with SHA256
2caba4377f003a6229585f1d559de6dedc1d5654e7f2566dcf9b98462c154525; hosted workflow 36237907349 passed all platform gates.
Lightweight Positioning
v1.3.0 remains the same stable protocol release surface as v1.0.0, not a workflow rewrite. The bridge does not introduce a daemon, service, database, custom DSL, independent state machine, or parallel task runner. It borrows useful ideas from Superspec, SuperB, and Comet at the diagnostic/documentation level (readiness checks, evidence rows, namespace validation, truthful demos), but keeps runtime ownership with upstream Spec Kit and Superpowers — and trusts upstream growth: Superpowers 6.4.2 is adapted through disposable task scaffolding, Spec Kit's native runtime events do not replace core-command lifecycle hooks, and v1.3.0 composes Spec Kit's markdown-driven hook mechanism and adds no parallel runner or planner.
AI-Assistance Disclosure
This extension is developed with AI coding assistants. Claude Code and Codex were used for design, planning, implementation, verification, and release-hardening passes. Every release artifact is reviewed by the maintainer before publication.
Testing Checklist
- Extension installs successfully via download URL.
- All commands execute without errors.
- Documentation is complete and accurate.
- No security vulnerabilities identified in the thin bridge package.
- Tested on real projects / end-user sandbox.
Submission Requirements
- Valid
extension.ymlmanifest included. - README.md with installation and usage instructions included.
- LICENSE file included.
- GitHub release created with version tag: https://github.com/lihan3238/speckit-superpowers-bridge/releases/tag/v1.3.0
- All command files exist and are properly formatted.
- Extension ID follows naming conventions: lowercase with hyphens.
Testing Details
Tested on:
- Linux bash / WSL2 with Spec Kit
1.0.12and audited Superpowers6.4.2. - Native Windows PowerShell 5.1 with the v1.3.0 public release artifact.
- GitHub-hosted native macOS bash for source/runtime portability coverage.
- Codex CLI
0.157.1. - Claude Code
2.1.283.
Test scenarios:
- Audited Spec Kit v1.0.12; refreshed tracked templates and bundled extension sources while preserving project-owned gates and bridge skills.
- Audited Superpowers
6.4.2; confirmed all invoked skill paths and the Task N adapter contract remain present. - Ran the full bash smoke suite (9/9), focused hook contract tests, the macOS/BSD path regression, shell syntax checks, and ShellCheck.
- Installed the public v1.3.0 ZIP in fresh WSL2/Linux and native Windows sibling sandboxes; the installed metadata reported 3 commands and 5 hooks.
- Ran package and release-readiness validators plus native Windows PowerShell coverage.
- Required Linux, Windows, and macOS release jobs to pass before publication.
- Drove complete handoff cycles in both sibling sandboxes; focused hook and adapter contract tests covered the markdown-driven hook behavior.
Example Usage
specify extension add speckit-superpowers-bridge --from https://github.com/lihan3238/speckit-superpowers-bridge/releases/latest/download/speckit-superpowers-bridge.zip
Then use the bridge from the active agent after Spec Kit has generated spec.md, plan.md, and tasks.md:
$speckit-superpowers-bridge
Claude Code users invoke the same bridge contract as:
/speckit-superpowers-bridge
Proposed Catalog Entry
{
"speckit-superpowers-bridge": {
"name": "Superpowers Implementation Bridge",
"id": "speckit-superpowers-bridge",
"description": "Thin orchestrator between Spec Kit (design) and Superpowers (implementation). Cross-agent.",
"author": "lihan3238",
"version": "1.3.0",
"download_url": "https://github.com/lihan3238/speckit-superpowers-bridge/releases/download/v1.3.0/speckit-superpowers-bridge-v1.3.0.zip",
"repository": "https://github.com/lihan3238/speckit-superpowers-bridge",
"homepage": "https://github.com/lihan3238/speckit-superpowers-bridge",
"documentation": "https://github.com/lihan3238/speckit-superpowers-bridge#readme",
"changelog": "https://github.com/lihan3238/speckit-superpowers-bridge/blob/main/CHANGELOG.md",
"license": "MIT",
"category": "process",
"effect": "read-write",
"requires": {
"speckit_version": ">=0.8.10",
"tools": [
{
"name": "powershell",
"version": ">=5.1",
"required": false
},
{
"name": "bash",
"version": ">=4.0",
"required": false
},
{
"name": "jq",
"version": ">=1.6",
"required": false
}
]
},
"provides": {
"commands": 3,
"hooks": 5
},
"tags": [
"bridge",
"superpowers",
"cross-agent",
"tdd",
"workflow"
],
"verified": false,
"downloads": 0,
"stars": 0,
"created_at": "2026-05-15T00:00:00Z",
"updated_at": "2026-09-26T00:00:00Z"
}
}
- Lingua principale
- Python
- Stelle
- 138k
- Fork
- 12.4k
- Merge medio
- 2g 11h
- PR unite (30g)
- 163
Preparare l'ambiente
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di github/spec-kit
-
Windows: Copilot integration hardcodes `copilot.cmd`, breaking installs that ship `copilot.exe`Apertabug-assess severity-medium triage-nice-to-have
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
github/spec-kit#4755 · 1 commento ·
I maintainer di solito rispondono entro 2 giorni
-
triage-nice-to-have
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
I maintainer di solito rispondono entro 2 giorni
-
[Feature]: 给 slug 添加默认值Apertaenhancement needs-triage triage-can-wait
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
github/spec-kit#4627 · 3 commenti ·
I maintainer di solito rispondono entro 2 giorni
-
needs-triage triage-nice-to-have
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
github/spec-kit#4527 · 1 commento ·
I maintainer di solito rispondono entro 2 giorni
-
bug-assess severity-medium
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
github/spec-kit#4273 · 3 commenti ·
I maintainer di solito rispondono entro 2 giorni
Tutte le issue di github/spec-kit
Issue simili
-
needs triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
openvinotoolkit/openvino_notebooks#3665 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
I maintainer di solito rispondono entro 1 giorno
-
docs
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
I maintainer di solito rispondono entro 1 giorno
-
benchmark-gap
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno