Summary
write-product-spec and spec-driven-implementation contradict each other on allowed specs/ directory naming.
The contradiction
.agents/skills/spec-driven-implementation/SKILL.md (line 24):
specs/ should contain only ticket-named directories as direct children. Do not create engineer-named subdirectories or feature-slug directories there.
.agents/skills/write-product-spec/SKILL.md (lines 25-29):
Write specs to specs/<id>/PRODUCT.md, where <id> is one of:
- a Linear ticket number
- a GitHub issue id, prefixed with
gh-
- a short kebab-case feature name
spec-driven-implementation explicitly prohibits feature-slug directories, while write-product-spec explicitly allows them.
Context
Discovered while porting these skills to a downstream repo. spec-driven-implementation also says to create a Linear issue before writing specs (line 26-27), which makes the feature-slug escape hatch unnecessary.
Suggested fix
Align write-product-spec with spec-driven-implementation: remove the feature-slug option, keep ticket IDs only (Linear or GitHub issue), and note that a ticket should be created first if none exists.
Summary
write-product-specandspec-driven-implementationcontradict each other on allowedspecs/directory naming.The contradiction
.agents/skills/spec-driven-implementation/SKILL.md(line 24):.agents/skills/write-product-spec/SKILL.md(lines 25-29):spec-driven-implementationexplicitly prohibits feature-slug directories, whilewrite-product-specexplicitly allows them.Context
Discovered while porting these skills to a downstream repo.
spec-driven-implementationalso says to create a Linear issue before writing specs (line 26-27), which makes the feature-slug escape hatch unnecessary.Suggested fix
Align
write-product-specwithspec-driven-implementation: remove the feature-slug option, keep ticket IDs only (Linear or GitHub issue), and note that a ticket should be created first if none exists.