You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actual scripts exist here: .specify/extensions/superb/scripts/powershell/sync-spec-status.ps1 .specify/extensions/superb/scripts/bash/sync-spec-status.sh
No wrapper exists at the old paths: .specify/scripts/powershell/sync-spec-status.ps1 .specify/scripts/bash/sync-spec-status.sh
Wrong references are in the generated/materialized agent and skill files: .agents/skills/speckit-superb-{controller,review,verify,finish}/SKILL.md .github/agents/speckit.superb.{controller,review,verify,finish}.agent.md
The extension command files under .specify/extensions/superb/commands/*.md use relative paths like scripts/powershell/sync-spec-status.ps1, which are correct if resolved relative to the extension root. The bad part is the materialized/global copies converting that into .specify/scripts/... instead of .specify/extensions/superb/scripts/....
Thank you for reporting this and providing such a clear analysis!
You are completely correct. The root cause lies in the specify CLI core code (located in the upstream spec-kit repository). Specifically, in specify_cli/agents.py, the path-adjusting method _adjust_script_paths (via rewrite_project_relative_paths) blindly rewrites relative scripts/ references in the command frontmatter to the project-level .specify/scripts/ directory, rather than preserving the extension-local paths under .specify/extensions/superb/scripts/.
Since this path-conversion behavior is managed by the core Spec Kit CLI compiler/runtime rather than the extension repository itself, this issue cannot be fixed directly within this spec-kit-extensions repository.
Suggested Resolution:
This needs to be fixed in the upstream spec-kit repository. We need to:
Update CommandRegistrar.rewrite_project_relative_paths and _adjust_script_paths in spec-kit's specify_cli/agents.py to accept an extension_id argument and resolve scripts relative to .specify/extensions/{extension_id}/scripts/ when installing extensions.
Update the command and skill generators in specify_cli/extensions/__init__.py to pass the correct extension_id during materialization.
I will flag this issue to the spec-kit maintainers to track and resolve the path conversion bug there.
Activity
RbBtSn0w commentedon Jun 25, 2026
Hi @csteeg,
Thank you for reporting this and providing such a clear analysis!
You are completely correct. The root cause lies in the
specifyCLI core code (located in the upstreamspec-kitrepository). Specifically, inspecify_cli/agents.py, the path-adjusting method_adjust_script_paths(viarewrite_project_relative_paths) blindly rewrites relativescripts/references in the command frontmatter to the project-level.specify/scripts/directory, rather than preserving the extension-local paths under.specify/extensions/superb/scripts/.Since this path-conversion behavior is managed by the core Spec Kit CLI compiler/runtime rather than the extension repository itself, this issue cannot be fixed directly within this
spec-kit-extensionsrepository.Suggested Resolution:
This needs to be fixed in the upstream
spec-kitrepository. We need to:CommandRegistrar.rewrite_project_relative_pathsand_adjust_script_pathsinspec-kit'sspecify_cli/agents.pyto accept anextension_idargument and resolve scripts relative to.specify/extensions/{extension_id}/scripts/when installing extensions.specify_cli/extensions/__init__.pyto pass the correctextension_idduring materialization.I will flag this issue to the
spec-kitmaintainers to track and resolve the path conversion bug there.