Should generated specifications be committed to a Git repository?

[Clement-Odrd]

Hello,

I'm using Speckit and I generated around 15 specs, now I'm wondering :

• Should I push the specs on my git repo or keep it local ?
• Is there any security risk to share it?

Thx for your help !

[genavico]

I was wondering the same thing. If we continue branching and merging, won't the codebase get filled up with /specs/* folders?

[mattseeger]

It does feel bloaty, but I am including them for the main reason that the quickstart.md files generated provide good documentation for the past later on.

The numbering of the specs becomes a problem

[marcindulak]

A similar question was asked in Fission-AI/OpenSpec#878

[mnriem]

It depends on what your workflow outside of Spec Kit is like. If you want to understand why certain ways where done the way they were the specs can tell you a lot. So then it would make sense. If you use Spec Kit as an execution engine for a traditional work item and that work item was already captured in your issue tracker, then the work item should be sufficient?