Status: Tier 2
Upstream spec-kit added an init flag to use YYYYMMDD-HHMM-feature instead of NNN-feature, removing the global-counter coordination problem on multi-contributor repos (commit 65ecd532, PR #1911).
What we'd build
Opt-in flag (probably surfaced via /iikit-core init --branch-style timestamp or a .specify/config.json setting) that switches create-new-feature.sh from NNN-* to YYYYMMDD-HHMM-* naming.
Active-feature cascade and specs/ directory layout stay unchanged — only the naming function differs.
Why it matters
Useful escape hatch for IIKit projects on busy multi-contributor repos where NNN counter collisions waste cycles (two devs start features simultaneously, both pick 005-*, merge conflict).
Optional, opt-in — defaults stay on NNN-*.
Evidence
- Upstream commit:
65ecd532 (#1911)
Cost
Small — branch-naming function + init flag + a .specify/config.json field.
Sequencing
Tier 2.
Status: Tier 2
Upstream spec-kit added an init flag to use
YYYYMMDD-HHMM-featureinstead ofNNN-feature, removing the global-counter coordination problem on multi-contributor repos (commit65ecd532, PR #1911).What we'd build
Opt-in flag (probably surfaced via
/iikit-core init --branch-style timestampor a.specify/config.jsonsetting) that switchescreate-new-feature.shfromNNN-*toYYYYMMDD-HHMM-*naming.Active-feature cascade and
specs/directory layout stay unchanged — only the naming function differs.Why it matters
Useful escape hatch for IIKit projects on busy multi-contributor repos where NNN counter collisions waste cycles (two devs start features simultaneously, both pick
005-*, merge conflict).Optional, opt-in — defaults stay on
NNN-*.Evidence
65ecd532(#1911)Cost
Small — branch-naming function + init flag + a
.specify/config.jsonfield.Sequencing
Tier 2.