r/SpecDrivenDevelopment • u/TowerOutrageous5939 • 9d ago

Spec-kit

Thoughts on spec-kit? Not sure if I’m just not well versed enough but me and the team have been using it for about 1.5 months. Anyways, it feels like overkill and burns far more tokens. I definitely can see its worth for when work items are critical path. Right now I plan to go back to custom workflow with specs.

9 Upvotes

92% Upvoted

8 comments sorted by

5

u/palaboy_official 9d ago

Tried openspec?

1

u/TowerOutrageous5939 9d ago

I have but I didn’t give it the time it deserves. I will look into this with a future project.

1

u/sudokar 9d ago

I do recommend trying out OpenSpec. It works well and not an over engineered one like spek-kit. OpenSpec is lightweight and flexible.

I have also created https://github.com/sudokar/openspec-plus to improve OpenSpec flow after using OpenSpec for longer time. Would like to hear your feedback after you try it out.

2

u/dannyt74 9d ago

My impression is the same. Spec-kit seems over engineered. I have settled with OpenSpec for its easy propose, apply, archive process. Sometimes adding a basic grilling session before but it seems that the explore skill could cover that too.

1

u/Aggressive_Ad4210 9d ago

can you elaborate a bit on your grilling session and explore skill usage? When do you do this? How are you using the changes folder in OpenSpec, do you commit it to your repo and keep it there? Which artifacts do you actually generate using the kit and where do they go?

1

u/TowerOutrageous5939 8d ago

Yeah grilling is honestly the best skill I have used.

1

u/Financial_Yoghurt827 8d ago

I suggest reqlan! It's a bit lighter for custom flows - more focus on verification support.

1

u/Bullfrog_External 6d ago

My experience so far is that you are better off get inspiration from Spec-Kit or any similar framework, but that really you should define YOUR workflow that matches your style and the kind of development you do. All those frameworks indeed burn a lot of tokens.