Bug: speckit.specify Sometimes Resets New Branch Name Back to 001 [already reported]

[uriel-kluk]

When running /speckit.specify, the tool normally creates a new numbered branch (e.g., 002-[story], 003-[another story], etc.).
However, in some cases, the branch number unexpectedly resets back to 001, even though a 001 branch already exists in the repository. This results in conflicts and manual cleanup.
This behavior seems intermittent.

Expected Behavior
speckit.specify should:

• Detect the highest existing numbered branch
• Create the next sequential branch (e.g., from 003 → 004)
• Never reuse an existing number

Actual Behavior

Branch generation occasionally resets to 001-[story]
This causes:

• naming collisions

[QC2168]

same issues

[fsilvaortiz]

This is the same root cause as #1744 — submitted a fix in PR #1757.

🤖 Generated with Claude Code