[Extension]: Update Superspec to v1.0.2

[CrazyBaran]

Note

This is an update to an existing catalog entry, not a new submission. The superspec extension is already in extensions/catalog.community.json at version 1.0.1. This submission bumps it to 1.0.2. Fields that change: version, download_url, stars, and updated_at. Everything else — description, tags, requires, provides — is unchanged.

Extension ID

superspec

Extension Name

Superspec

Version

1.0.2

Description

Bridges spec-kit workflows with obra/superpowers capabilities for brainstorming, TDD, code review, and resumable execution.

Author

WangX0111

Repository URL

https://github.com/WangX0111/superspec

Download URL

https://github.com/WangX0111/superspec/archive/refs/tags/v1.0.2.zip

License

MIT

Homepage (optional)

https://github.com/WangX0111/superspec

Documentation URL (optional)

https://github.com/WangX0111/superspec/blob/main/README.md

Changelog URL (optional)

https://github.com/WangX0111/superspec/blob/main/CHANGELOG.md

Required Spec Kit Version

=0.1.0

Required Tools (optional)

None required. Optionally detects obra/superpowers skills (brainstorming, writing-plans, executing-plans, subagent-driven-development, test-driven-development, requesting-code-review) if installed, and falls back to built-in behavior otherwise — unchanged from the current 1.0.1 entry.

Number of Commands

5

Number of Hooks (optional)

3

Tags

superpowers, brainstorming, tdd, code-review, subagent, workflow

Key Features

What 1.0.2 changes vs. 1.0.1 (full detail in CHANGELOG.md):

• Fixes the v1.0.1 install failure (WangX0111/superspec#6). v1.0.1 could not be installed via specify extension add superspec: the catalog downloads GitHub's generated tag ZIP, spec-kit's _download_security.py rejects any archive member over 10 MiB, and assets/workflow-overview-en.png in that tag was ~12 MiB, so installs aborted with ZIP member ... exceeds maximum size of 10485760 bytes. The 1.0.2 tag archive ships only the runtime payload — verified directly below.
• .gitattributes marks documentation media (assets/), samples (examples/), dev tooling (scripts/), and CI (.github/) as export-ignore, so git archive — and therefore GitHub's generated tag ZIP — omits them. The repository itself, the rendered README images, and --dev installs are unchanged; nothing was deleted.
• Documentation now reflects spec-kit's real specs/NNN-*/ feature layout instead of the previous .specify/specs/ convention.
• New CI step: scripts/validate-release-archive.py rebuilds the published archive and is meant to fail the build if it approaches a spec-kit install limit, drops a file extension.yml declares, or regains an export-ignored path (see Testing Details for a caveat — this step didn't get to run for this specific tag).

Testing Checklist

• Extension installs successfully via download URL
• All commands execute without errors
• Documentation is complete and accurate
• No security vulnerabilities identified
• Tested on at least one real project

Submission Requirements

• Valid extension.yml manifest included
• README.md with installation and usage instructions
• LICENSE file included
• GitHub release created with version tag
• All command files exist and are properly formatted
• Extension ID follows naming conventions (lowercase-with-hyphens)

Testing Details

Direct verification performed for this submission (2026-08-14):

• Downloaded https://github.com/WangX0111/superspec/archive/refs/tags/v1.0.2.zip directly: HTTP 200, 45,776 bytes, 25 entries, largest member ~0.02 MiB — well under spec-kit's 10 MiB/member and 50 MiB/total install limits. This confirms the archive-size fix described in the CHANGELOG for the v1.0.1 bug actually holds in the published tag artifact itself, not just in source.
• Unzipped and inspected extension.yml from inside that exact archive: id: "superspec", version: "1.0.2", all 5 commands (speckit.superspec.{status,brainstorm,tasks,execute,review}) and all 3 hooks (after_tasks, before_implement, after_implement) correctly namespaced under speckit.superspec.*.

Known CI caveat, disclosed for transparency: the repository's own CI workflow is currently failing on the v1.0.2 tag / main commit (c20ac6c) at its first step, validate-extension-metadata.py:

FAIL: command 'constitution-template' must use namespace 'speckit.superspec.*' (matching extension.id='superspec')

This is a false positive in that script's own re-implementation of the namespace rule, not a real defect: its command-name regex (^ - name:) matches any 4-space-indented - name: line in extension.yml, so it also sweeps up the provides.templates entries (e.g. constitution-template) and wrongly demands they carry the command-namespace prefix, which template names were never meant to have. Because that step fails first, the CI job's later, more meaningful step — Verify install with latest spec-kit, which actually runs specify extension add "$GITHUB_WORKSPACE" --dev against a real spec-kit checkout and greps the resulting .specify/extensions.yml for speckit.superspec.{tasks,execute,review} — never got to run for this tag. I could not run that exact step myself either: specify init needs an interactive TTY for its setup confirmation in this sandboxed shell, and two attempts (with and without --offline) blocked waiting on stdin until timeout. So the direct archive/manifest inspection above is real, but it's not a substitute for that end-to-end CI step actually passing. Flagging both the false positive and the untested gap rather than omitting either.

Example Usage

# Install (add --force when upgrading an existing v1.0.1 install)
specify extension add superspec --from https://github.com/WangX0111/superspec/archive/refs/tags/v1.0.2.zip --force

# Status / next-step suggestion
/speckit.superspec.status

# Brainstorm edge cases for a spec
/speckit.superspec.brainstorm specs/001-user-authentication/spec.md

# Task breakdown, execution, and review
/speckit.superspec.tasks
/speckit.superspec.execute
/speckit.superspec.review

Proposed Catalog Entry

{
  "superspec": {
    "name": "Superspec",
    "id": "superspec",
    "description": "Bridges spec-kit workflows with obra/superpowers capabilities for brainstorming, TDD, code review, and resumable execution.",
    "author": "WangX0111",
    "version": "1.0.2",
    "download_url": "https://github.com/WangX0111/superspec/archive/refs/tags/v1.0.2.zip",
    "repository": "https://github.com/WangX0111/superspec",
    "homepage": "https://github.com/WangX0111/superspec",
    "documentation": "https://github.com/WangX0111/superspec/blob/main/README.md",
    "changelog": "https://github.com/WangX0111/superspec/blob/main/CHANGELOG.md",
    "license": "MIT",
    "requires": {
      "speckit_version": ">=0.1.0"
    },
    "provides": {
      "commands": 5,
      "hooks": 3
    },
    "tags": [
      "superpowers",
      "brainstorming",
      "tdd",
      "code-review",
      "subagent",
      "workflow"
    ],
    "verified": false,
    "downloads": 0,
    "stars": 60,
    "created_at": "2026-04-22T00:00:00Z",
    "updated_at": "2026-08-14T00:00:00Z"
  }
}

Additional Context

Diff against the current catalog entry, for reviewer convenience — only these fields change:

Field	Current	Proposed
version	1.0.1	1.0.2
download_url	.../tags/v1.0.1.zip	.../tags/v1.0.2.zip
stars	0	60
updated_at	2026-05-30T00:00:00Z	2026-08-14T00:00:00Z

created_at, provides (5 commands / 3 hooks), requires, tags, description, verified, and downloads are unchanged. stars is schema-marked auto-updated, so please treat 60 as informational (current live count at submission time).

Release: https://github.com/WangX0111/superspec/releases/tag/v1.0.2

Prior history for this entry: added as superpowers-bridge v1.0.0 via #2309, then renamed to superspec and bumped to v1.0.1 via #2772 (both merged directly, predating the current issue-driven submission flow). This is the first submission for this extension going through the Extension Submission issue template.

Two things noticed while preparing this that are not part of the requested change, flagged for a maintainer to weigh in on rather than acted on unilaterally:

1. The catalog's display name for this entry is "Superspec", while extension.yml's own extension.name field and the README title both say "Superpowers Bridge". Left as-is here to keep this a pure version bump; worth aligning whenever this entry is next touched.
2. See the CI caveat under Testing Details above — the upstream repository's own Validate extension check is currently red on this tag due to a false positive in its local validator script, unrelated to the real spec-kit namespace rule.

---

This issue was drafted and filed by Claude (Sonnet 5).

[github-actions]

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

[github-actions]

Pull request created: #4120

Generated by Add Community Extension from Issue Submission · 227.5 AIC · ⌖ 16.1 AIC · ⊞ 35.3K

[mnriem]

Thank you!