Status: Tier 2
Upstream spec-kit accepts single-segment gitflow branch prefixes — branches matching <prefix>/NNN-name (e.g., feat/001-user-auth, fix/042-null-deref) resolve to specs/001-user-auth/ (commit 4687c33b, PR #2202).
What we'd build
Adjust the branch-detection regex in iikit-core/scripts/bash/ so the active-feature cascade recognizes both:
NNN-name (current — branch root)<segment>/NNN-name (new — gitflow prefix)
The CLAUDE.md cascade order stays the same:
.specify/active-feature fileSPECIFY_FEATURE env var- Git branch (now:
NNN-* OR <prefix>/NNN-*)
- Single feature auto-select
Why it matters
Many teams use gitflow conventions (feat/, fix/, chore/). Today IIKit's active-feature cascade silently falls through to "single feature auto-select" or fails on them, which is confusing on multi-feature projects.
Removes friction for new adopters without changing the cascade semantics.
Evidence
- Upstream commit:
4687c33b (#2202)
Cost
Small — adjust the branch-detection regex in iikit-core/scripts/bash/.
Sequencing
Tier 2.
Status: Tier 2
Upstream spec-kit accepts single-segment gitflow branch prefixes — branches matching
<prefix>/NNN-name(e.g.,feat/001-user-auth,fix/042-null-deref) resolve tospecs/001-user-auth/(commit4687c33b, PR #2202).What we'd build
Adjust the branch-detection regex in
iikit-core/scripts/bash/so the active-feature cascade recognizes both:NNN-name(current — branch root)<segment>/NNN-name(new — gitflow prefix)The CLAUDE.md cascade order stays the same:
.specify/active-featurefileSPECIFY_FEATUREenv varNNN-*OR<prefix>/NNN-*)Why it matters
Many teams use gitflow conventions (
feat/,fix/,chore/). Today IIKit's active-feature cascade silently falls through to "single feature auto-select" or fails on them, which is confusing on multi-feature projects.Removes friction for new adopters without changing the cascade semantics.
Evidence
4687c33b(#2202)Cost
Small — adjust the branch-detection regex in
iikit-core/scripts/bash/.Sequencing
Tier 2.