Remove all git functionality.

[airtonix]

It's just going to get in the way.

• not everyone is going to appreciate the branch naming convention you're imposing here
• using the branch name as a way to indicate the current spec being worked on is insufficient for teams that prefer small PRs with different branch names for the actual implementation stage.
• using the git repo root as the spec location will not work for people in monorepos that want to put the specs next to the app or pkg they are working on.

if git functionality is super-absolute-non-negotiable (i'd argue it's not relevant tbh) then #536

[sanathusk]

+1, The user should be presented with a choice

[Etsija]

The only reason preventing me from using spec-kit atm is I handle all git-specific with GitButler (terrific tool btw) and spec-kit's mandatory branch creation would just ruin GB use for me. So, yes, it should at least be optional.

[Rep0se]

I had to add a workaround into my agent's memory to remove Git operations, so every time I update Spec Kit, I have to remove automatic Git branch creation from create-new-feature.ps1

[airtonix]

I created a gitless version for myself https://github.com/zenobi-us/speckit-remix