Improve Branching

[josephcrawfordSRH]

On our team we tend to create branches that coincide with jira tickets such as bug/FL-123, however when I use spec-kit I can see that it tries to create branches for me such as 001-this-is-a-task. This truly does not make sense with our workflow as these branches will not appear on our jira tickets without being named properly.

I would love to see this allow us to specify a branch or take instructions on what branch should be used for the spec.

This is the only thing holding us back from adopting this tool in our process full-time. I have worked with it a bit and I can see that eventually it will realize that you are on a custom branch and load the spec from known folders but sometimes this does not work and it will put me on a new branch unexpectedly.

If this is possible and I am missing something please let me know, would love to use this full-time.

[michaelerobertsjr]

Would this support your use case: 1067

[josephcrawfordSRH]

I do not think so, this seems to only tell spec-kit where you want your spec files to go if not for specs/, what I am looking for is something like /speckit.specify bug/FL-123 This is a bugfix for an issue. and then have it generate the /specs/FL-123/spec.md etc. It should also see that bug/FL-123 should be the branch name so rather than creating 001-this-is-a-bugfix it would just either create or use bug/FL-123 as the git branch for the specification.

[peterHoburg]

Here is a PR that might solve your issue #1117

[josephcrawfordSRH]

Ahh yea that will do it, cannot wait to see that get released, thank you!