Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From speckit-dev
Publish and distribute a GitHub spec-kit extension — cut a GitHub release, write the catalog entry, and register it in a catalog. Defaults to the team catalog nq-rdl/spec-kit-extensions; also covers the public community catalog submission. Use when releasing/distributing/sharing a spec-kit extension, adding a catalog entry, or when the user runs /speckit-dev:publish.
How this skill is triggered — by the user, by Claude, or both
Slash command
/speckit-dev:publish Which extension to publish, and where? (default target: nq-rdl/spec-kit-extensions)Which extension to publish, and where? (default target: nq-rdl/spec-kit-extensions)The summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Verify-canonical guard.** Publishing/catalog pinned to spec-kit v0.12.x /
Verify-canonical guard. Publishing/catalog pinned to spec-kit v0.12.x / catalog schema_version 1.0 (2026-07-04). Confirm against
references/publishing.rstand the live publishing guide.
Team default: the team catalog nq-rdl/spec-kit-extensions — add a
catalog entry there (installable, install_allowed: true). Consumers wire it via
.specify/extension-catalogs.yml (see /speckit-dev:manage).
Public community catalog (github/spec-kit): submit via the
extension_submission.yml issue template — NOT a direct PR to
catalog.community.json. Review 3–7 business days.
The /speckit-dev:publish invocation also triggers the speckit-publish-target
hook, which reminds you of the default target.
vX.Y.Z in the extension repo → archive at
.../archive/refs/tags/vX.Y.Z.zip.sha256 of the archive (recommended; verified before install).references/publishing.rst; sample in
assets/catalog-entry.json).nq-rdl/spec-kit-extensions's catalog.json.
Community: file the submission issue template.See references/publishing.rst and references/canonical-sources.rst.
npx claudepluginhub nq-rdl/agent-extensions --plugin speckit-devGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.