You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on a sample project to see if spec-kit works any better than my own spec-driven workflow, and was surprised to see that actually compiling and executing code wasn't in there. After executing on the plan and tasks Claude just generated dozens of classes, but they had hundreds of compilation errors as the AI never bothered to try compiling them. Forget actually working, the AI code won't even compile. It did create unit tests, but of course those don't compile either.
Interating over new code until it compiles and passes unit tests is baked into my own spec-driven AI workflow, so I am surprised something so basic wouldn't be included here. Is that something I did wrong?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'm working on a sample project to see if spec-kit works any better than my own spec-driven workflow, and was surprised to see that actually compiling and executing code wasn't in there. After executing on the plan and tasks Claude just generated dozens of classes, but they had hundreds of compilation errors as the AI never bothered to try compiling them. Forget actually working, the AI code won't even compile. It did create unit tests, but of course those don't compile either.
Interating over new code until it compiles and passes unit tests is baked into my own spec-driven AI workflow, so I am surprised something so basic wouldn't be included here. Is that something I did wrong?
Beta Was this translation helpful? Give feedback.
All reactions