What best practices exist for concurrent SpecKit development?

[EmadMokhtar]

Hi,

I’m working with SpecKit and I’m concerned about how a team can collaborate without running into conflicts. Because SpecKit’s specs are sequentially numbered, it can be difficult to avoid clashes when multiple engineers are creating specs concurrently.

Example

A repository already contains three specs. Two engineers each create a short‑lived feature branch to implement new features. Using SpecKit, both engineers would try to create the next spec, 0004, which will inevitably cause a merge conflict.

Question

What strategies does SpecKit recommend to prevent such conflicts?

• Does the SpecKit team provide guidelines or tooling for concurrent spec creation in a multi‑engineer environment?
• Are there recommended branching or spec‑numbering workflows that teams can adopt to avoid these merge conflicts?

[mnriem]

I would say define who is the source of truth for:

1. The branch naming
2. The feature spec directory naming

Then when you go through the process you specifically guide the commands to use those

PS. we have a PR in flight that will hopefully make that a bit smoother