-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Description
Hi team, first off, thank you for the great work on the Spec-kit project — it’s been very helpful and has lot of great ideas.
I ran into a couple of challenges that I think might be worth discussing:
-
Cross-platform script selection during initialization
When initializing a new project, Spec-kit currently asks whether to use Bash or PowerShell. This works fine for an individual, but can create issues in multi-OS environments.
For example, if one developer initializes the project on Windows and selects PowerShell, teammates using macOS will encounter errors when trying to run commands, since PowerShell isn’t available by default on Mac.
This can become a friction point for mixed teams or larger organizations with diverse development environments. -
Code duplication across repositories
It seems that a large amount of build/setup code from this project gets duplicated across every repository that depends on it. In an enterprise environment with tens of thousands of repositories, maintaining and updating these scripts can become quite cumbersome.
Potential improvements
Here are a few ideas that might help address these points:
Avoid using separate shell scripts altogether — consider moving the logic directly into the library and exposing it via the CLI.
If scripts are necessary, you could look into solutions such as git-hook/post-clone to allow script customization while keeping them out of version control (e.g., in a .gitignore folder).
Thanks again for your hard work and for considering this feedback — happy to discuss or help test alternative approaches if that’s helpful.