Sounds great, what I wonder is how you treat edge cases that your Ai requirement phase identifies. Do you let Ai decide how to handle them or do you jump in and review/adjust manually. I'm currently getting my hands dirty with spec kit and feel like I write very detailed specifications. Still edge cases occur regularly where I then adjust the spec or plan.
In my requirement review and design review phase, I specific that the agent need to review edge cases and come up with 3 suggestions. So that I can choose. In case it is not match my expectation I will tell it to remember the case and provide answer for it to remember.
I just want to say i appreciate you wrote the article and do your own writing. I dont really understand what your trying to say (something analogous to omc/ulw?) but i appreciate it
I wrote the full breakdown here: https://codeaholicguy.com/2026/04/11/how-my-ai-workflow-evol...
Sounds great, what I wonder is how you treat edge cases that your Ai requirement phase identifies. Do you let Ai decide how to handle them or do you jump in and review/adjust manually. I'm currently getting my hands dirty with spec kit and feel like I write very detailed specifications. Still edge cases occur regularly where I then adjust the spec or plan.
In my requirement review and design review phase, I specific that the agent need to review edge cases and come up with 3 suggestions. So that I can choose. In case it is not match my expectation I will tell it to remember the case and provide answer for it to remember.
Nice, maybe I'll give devkit a try to compare it to the spec kit approach.
Appreciate it, I know there are so much room to improve, looking forward to hearing feedback from you.
I just want to say i appreciate you wrote the article and do your own writing. I dont really understand what your trying to say (something analogous to omc/ulw?) but i appreciate it
Thank you, appreciate it
Great question! I have been thinking about this too and would love to hear what approaches others have tried.