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
When I run the /specify command, it creates a new specs folder that is outside of the folder. This was unexpected as we typically have main 'code' directory with sub folder where each project folder is located. So while we have the Spec-kit project folder open in VS Code, after running the /spec command we have to browse back out to the parent folder that hosts other project folders to access the 'spec' folder. I would think the spec folder should be located in the main project folder and not outside. Is this by design?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
When I run the /specify command, it creates a new specs folder that is outside of the folder. This was unexpected as we typically have main 'code' directory with sub folder where each project folder is located. So while we have the Spec-kit project folder open in VS Code, after running the /spec command we have to browse back out to the parent folder that hosts other project folders to access the 'spec' folder. I would think the spec folder should be located in the main project folder and not outside. Is this by design?
Thanks,
LJ
Beta Was this translation helpful? Give feedback.
All reactions