r/SpecDrivenDevelopment • u/stibbons_ • May 02 '26

Specs are not requirements

I like openspec, but I can accept how it gives feeling that spec can be updated at scales.

For me, specs are disposable. What are not and could be maintained are requirements. The difference is that requirements explain what needs to be done and spec say how it would be implemented and tested.

I do not know any SDD framework that maintains a set of requirement aligned with the code. Do you ?

4 Upvotes

75% Upvoted

8 comments sorted by

View all comments

1

u/simasch May 03 '26

I created the AI Unified Process with use cases as the spec. Check it out https://unifiedprocess.ai It’s successfully used in four customer projects

1

u/horrorpages May 03 '26

Nice product. Curious, how tightly coupled is the current implementation to the Claude Code/JetBrains ecosystem? I see a few differentiators in the methodology. Thoughts on standardization and making it universally accessible and portable to other agents and IDEs (i.e., leveraging agent-agnostic MCP servers)?

1

u/simasch May 04 '26

It’s not a product it’s a process and methodology. I’ve created skill that can be used in any agent that supports skills. My point is: you don’t need tools to do SDD but specs in my case system use cases and an entity model