[Extension]: Update speckit-superpowers-bridge to v1.2.0

[lihan3238]

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.2.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

https://github.com/lihan3238/speckit-superpowers-bridge/releases/latest/download/speckit-superpowers-bridge.zip

Version-pinned artifact:

https://github.com/lihan3238/speckit-superpowers-bridge/releases/download/v1.2.0/speckit-superpowers-bridge-v1.2.0.zip

The catalog download_url intentionally remains the stable latest-release alias. Since v0.6.0 every release uploads both the versioned ZIP and speckit-superpowers-bridge.zip; future catalog updates should bump only version unless the distribution policy changes.

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.2.0:

• Spec Kit 0.16.4 for repository bootstrap, Linux bash verification, and the v1.2.0 release sandbox; bridge runtime floor remains >=0.8.10.
• Superpowers 6.3.0.
• Codex CLI 0.147.0.
• Claude Code 2.1.233.

Required Tools

• PowerShell >=5.1 for the Windows runtime flavor.
• Bash >=4.0 and jq >=1.6 for 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 -Readiness read-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-class category: process / effect: read-write manifest fields introduced by Spec Kit 0.10.2, backward compatible with the >=0.8.10 runtime 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-development reviewer-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.0 after all six invoked skill names and the Spec Kit tasks.md consumption boundary were re-audited.
• New in v1.2.0: plug-and-play before_implement / after_implement extension-hook dispatch from PR feat: Add Codex CLI support #14, hardened to Spec Kit 0.16.4 semantics. Mandatory hooks emit EXECUTE_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 Fix template path in plan command #13 by removing GNU-only realpath -m from the bash handoff writer. Portable, symlink-aware missing-path normalization now works on standard macOS without GNU coreutils.

Support Matrix

Target	Result	Evidence
Linux bash	PASS	bash tests/run-all.sh (8/8) on Spec Kit 0.16.4, source/package validators, and the public-v1.2.0 WSL2 sandbox cycle.
Windows PowerShell 5.1+	PASS	Native tests/test-release-powershell.ps1, readiness validation, and the public-v1.2.0 Windows sandbox cycle.
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.2.0 implementation, source verification, and public-artifact cycle with Codex CLI 0.147.0.
Claude Code	PASS	Claude Code 2.1.233 integration/skill contract verification recorded in the v1.2.0 feature evidence.

Release Validation Summary

• scripts/release/validate-release-readiness.ps1 -Version 1.2.0 -PackageZip dist/speckit-superpowers-bridge-v1.2.0.zip passes.
• scripts/release/test-validate-release-readiness.ps1 passes, 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.sh passes.
• tests/test-release-powershell.ps1 passes under Windows PowerShell.
• The macOS-hosted release gate passes the full bash suite and focused handoff portability regression.
• Final v1.2.0 ZIP SHA256 is recorded in the GitHub release notes for both the versioned ZIP and the stable latest alias.

Lightweight Positioning

v1.2.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.3.0 needs no bridge shim, Spec Kit's native runtime events do not replace core-command lifecycle hooks, and v1.2.0 composes Spec Kit's markdown-driven hook mechanism rather than adding a runner.

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.yml manifest 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.2.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 0.16.4 and audited Superpowers 6.3.0.
• Native Windows PowerShell 5.1 with the v1.2.0 public release artifact.
• GitHub-hosted native macOS bash for source/runtime portability coverage.
• Codex CLI 0.147.0.
• Claude Code 2.1.233.

Test scenarios:

1. Audited Spec Kit 0.11.1 → 0.16.4; refreshed tracked templates and bundled extension sources while preserving project-owned gates and bridge skills.
2. Audited Superpowers 6.3.0; confirmed all six invoked skill paths and the Spec Kit tasks.md consumer contract remain present.
3. Ran the full bash smoke suite (8/8), focused hook contract tests, the macOS/BSD path regression, shell syntax checks, and ShellCheck.
4. Registered the v1.2.0 bridge from a safe temporary --dev copy in the source checkout; installed metadata reported Category: process, Effect: read-write, 3 commands, and 5 hooks.
5. Ran package and release-readiness validators plus native Windows PowerShell coverage.
6. Required Linux, Windows, and macOS release jobs to pass before publication.
7. Installed the public v1.2.0 ZIP in the WSL2 and Windows sibling sandboxes and drove complete handoff cycles, including synthetic implement hooks.

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.2.0",
    "download_url": "https://github.com/lihan3238/speckit-superpowers-bridge/releases/latest/download/speckit-superpowers-bridge.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-08-18T00:00:00Z"
  }
}

[github-actions]

cc @github/spec-kit-maintainers — new catalog submission for review.

[github-actions]

Pull request created: #4183

Generated by Add Community Extension from Issue Submission · 295 AIC · ⌖ 16.2 AIC · ⊞ 35.3K

[mnriem]

Heads-up on the catalog download_url for this entry, @lihan3238 — resolved in #4183.

The submission (and this issue) sets the catalog download_url to the floating releases/latest/download/speckit-superpowers-bridge.zip alias, with the note that future updates should bump only version. We can't take the floating alias in the catalog:

• Spec Kit catalog entries pin each version to an immutable, tag-scoped artifact — releases/download/<tag>/<asset>.zip. Every other entry follows this, and it's the pattern required by the add-community-extension workflow (Step 2d).
• A version: 1.2.0 record pointing at /latest/ would silently serve your future releases under the 1.2.0 pin, which breaks reproducibility for anyone installing the pinned version.

So #4183 pins to the versioned asset you already publish:

https://github.com/lihan3238/speckit-superpowers-bridge/releases/download/v1.2.0/speckit-superpowers-bridge-v1.2.0.zip

Nothing changes on your side — keep publishing both the versioned ZIP and the -latest alias if you like; the catalog will just always reference the immutable versioned asset, and each new version needs a one-line download_url bump alongside version. We're codifying this as a hard validation rule (and rejecting releases/latest/) in #4185.

---

Posted on behalf of @mnriem by GitHub Copilot (model: claude-opus-4.8, supervised).

[mnriem]

Note that previously the agentic workflow made it appear it was a soft requirement. It actually is required to have tagged versions

[mnriem]

Thank you!