Do you have a patch for this behavior change? It could be a config option...defaults become a recommendation. I have gotten asks about customizing or outright changing this workflow, too.

I'd appreciate if it was clearer what Spec-Kit expected for branch names. I tried starting on my own branch, but the scripts errored out. When that didn't work. Claude was happy to "work around it", but I don't know what I was missing from not actually running the scripts. So I had to dump that whole branch and restart the process and let Spec-Kit make the branch itself.

Another area that is murky for me after reading the docs is how often I can merge. For an MVP I'd prefer to merge after every step so there's a clean history in the repo, but Spec-Kit seems to want to do an entire spec in one branch. That means you have to go look on that branch to see the history since our repos default to Squash and Merge.

Regardless of what the Spec-Kit strategy is it would be nice if it were documented somewhere:

• what the acceptable branch names are
• when it is ok to merge

As a bonus, make the branch naming strategy pluggable so we can override the opinionated default to work smoother in opinionated organizations.

I want to decide when to create a branch and what to name it. I do not want Spec-Kit to do that for me. Each team will have its own branching strategy and naming conventions, which may not be compatible with the Spec-Kit branching strategy and convention.

At the very least, there should be a configuration option in Spec-Kit to skip the branch creation.