Replies: 1 comment 1 reply
-
|
I think it depends on workflow. For Greenfield it could be, for bugfixes not. This approach has 4-cycle approach dediceted more for management team nither for role-specific(dev, qa) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
First of all, I want to express my respect — I really liked the methodology of Spec Driven Development.
I find the idea logical — that with the rise of AI, the level of abstraction will increase, and code will become what bytecode or machine code is today: a generated artifact nobody looks at. It’s a beautiful idea, and I like it.
In the official approach. It says things like:
But I’ve been integrating speckit into my project for a couple of weeks now, and I noticed the following:
So despite the declared approach, the SOURCE OF TRUTH IS STILL THE CODE.
I don’t want to offend anyone, I really appreciate the work that’s been done, but this gap is kind of disorienting to me.
@localden Please tell, is this difference between the philosophy and the actual behavior just temporary, or is it a planned part of the concept?
Beta Was this translation helpful? Give feedback.
All reactions