[Bug]: Not able to add the extensions

[vamshikrishnamraju]

Bug Description

When trying to add the extension i am getting Validation error.

specify extension add verify --from https://github.com/ismaelJimenez/spec-kit-verify/archive/refs/tags/v1.0.0.zip
Warning: Installing from external URL.
Only install extensions from sources you trust.

Downloading from https://github.com/ismaelJimenez/spec-kit-verify/archive/refs/tags/v1.0.0.zip...

Validation Error: Invalid alias 'speckit.verify': must follow pattern 'speckit.{extension}.{command}'

speckit version details

CLI Version 0.5.1.dev0 │
│ Template Version 0.5.0 │
│ Released 2026-04-02 │
│ │
│ Python 3.12.6 │
│ Platform Windows │
│ Architecture AMD64 │
│ OS Version 10.0.26200 │
│

Steps to Reproduce

specify extension add verify --from https://github.com/ismaelJimenez/spec-kit-verify/archive/refs/tags/v1.0.0.zip

Expected Behavior

Expected to install the extension without any error

Actual Behavior

Validation Error: Invalid alias 'speckit.verify': must follow pattern 'speckit.{extension}.{command}'

Specify CLI Version

0.5.0

AI Agent

GitHub Copilot

Operating System

Windows

Python Version

3.12.6

Error Logs

Validation Error: Invalid alias 'speckit.verify': must follow pattern 'speckit.{extension}.{command}'

Additional Context

I tried with multiple extensions, i am getting the same error

[carlosfiori]

Same here on version 0.5.1.dev0:

[mnriem]

You'll have to ask the extension developer to adhere to the new naming scheme as extension are no longer allowed to use the /speckit prefix. Note this was done so it is clear the command is coming from an extension.

[gatuno1]

Is there any way to mitigate this?
Well, with a fresh install of this version, you can no longer install any extensions!
It doesn't sound very realistic to ask each and every developer to switch to the new naming scheme. Perhaps there are sufficient technical reasons to justify the new scheme, but in practice, it disables the entire community ecosystem...

[mnriem]

@gatuno1 We have restored the alias shadowing for now. But we will follow this up with another PR soon that will flag this as deprecated behavior and disallow it in a future release (likely 1.0.0) as this can override other registered commands