/specify new branch problems

[airtonGit]

This feature of suggest and create a new branch is very fragile when using git worktrees, can I ask to just work in actual branch?

[localden]

@airtonGit can you tell me more about your workflow and what could work better there?

[airtonGit]

I’ve been experimenting with different ways of working, refining the initial /spec and /plan prompts between Copilot and Claude Code. Now I want to test Claude Code sub-agents, so I opened a new git worktree for this test:

1. In this worktree I already have a specific branch checked out — I can’t switch back to develop here, and this already creates some friction with /spec.

2. somehow /spec managed to move forward on the branch I’m in, but /plan got lost and started reading the spec.md from another git worktree that also contains spec-kit files...

[flavour]

#61

[rogadev]

#521 I expanded a bit on this, but I also think a new command like /rename or /rename-spec is an important feature.

Maybe AI picked a terrible name. Maybe you built out the spec and then realized "oops", maybe this isn't a feature we're building, or we're going a new direction now. Things happen.

Currently, deleting a folder with a name you don't like will still see it re-generate the next time you hit /specify. This is not ideal. It's creating useless artifacts in our projects.

Lastly, a branch naming schema like ###-generated-name when every other branch is named differently does tend to call developers out on the tools they're using. Some users might want to have control over the exact name that /specify generates and I think that's an important consideration.

[raulduk3]

Very true. My workaround has been deleting both the folder and branch. I think managing the Git repo is something that can be clarified per project constitution.

[Desgue]

Sorry to highjack this issue, i dont know if its relevant to create a new issue for this.

But /specify command will use the firs few words of the prompt for the branch name, for example /specify I am building a modern resume creation website that uses AI to generate formatting and text reads human and not AI like. Should have a landing page, an about page, a FAQ page and a Resume generation page. We wont have auth or multi tenant. This is an mvp so bare minimum functionality. and the branch generated by this is 001-i-am-building.

I find this annoying and not very intuitive.

[jcastillopino]

@localden I have created PR #579 that generates feature names from descriptions using AI, while maintaining full backward compatibility. You can even give the feature name explicitly.