Repository navigation
[Bug]: Adding spec-kit to an existent project does not creates spec.md files #2506
Description
Bug Description
When adding spec-kit to an nx monorepo folder the cli fails silently after changing branches without creating any spec.md file
Steps to Reproduce
- Create a nx
npx create-nx-workspace@latest(angular in my case) - Initialize spec-kit there (agent claude)
- define the constitution
- run /speckit-specify on claude-code vscode plugin
Expected Behavior
The spec/001-feature/spec.md file should exists.
Actual Behavior
no spec.md file is created.
Specify CLI Version
0.8.7
AI Agent
Claude Code
Operating System
macOS 26.3.1 (a)
Python Version
Python 3.14.4
Error Logs
No error logsAdditional Context
No response
Activity
mnriem commentedon May 11, 2026
Can you verify the version using
specify --versionorspecify version?distante commentedon May 11, 2026
mnriem commentedon May 12, 2026
First off I have no clue how the
claude-code vscode pluginoperates but I suspect there might be an issue there. Second the specs would be found in thespecsdirectory. In order to help you better I need more information / logs. Can you be a bit more specific for each step?distante commentedon May 12, 2026
There were no logs, the agent finished and no specs where created. Using it on claude on the terminal worked as expected. So we could just close this as an external error...?
mnriem commentedon May 12, 2026
So that means that it seems to behave differently depending on where Claude is running.
Closing it as suggested