speckit-dev

Scaffold a new GitHub spec-kit extension — the extension.yml manifest, commands/*.md, an optional config template, and .extensionignore — valid by construction. Use when creating a spec-kit extension, authoring a speckit.<id>.<cmd> command, adding a quality-gate/integration/hook to the Spec-Driven-Development workflow, or when the user runs /speckit-dev:create. spec-kit ships no `specify extension init`, so this fills the scaffolding gap. Distinct from Claude Code plugins/skills and from OpenCode extensions.

Install, list, enable/disable, update, and configure GitHub spec-kit extensions, and manage the catalog stack. Use when running `specify extension` commands, wiring a team/internal catalog, resolving the PyPI specify-cli install footgun, configuring .specify/extension-catalogs.yml or extensions.yml, or when the user runs /speckit-dev:manage.

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.

Lint an existing GitHub spec-kit extension against the real manifest schema and validation rules, and report pass/fail per rule. Use when checking a spec-kit extension before install/publish, debugging a `specify extension add` rejection, auditing extension.yml / commands/*.md, or when the user runs /speckit-dev:validate. Mirrors the checks spec-kit's ExtensionManifest performs at install time.

1 hook across 1 event