The latest articles on DEV Community by abinavrockss (@abinavrockss). https://dev.to/abinavrockss https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F531221%2F552e4414-3dcc-4894-b324-2867e8cfd073.png https://dev.to/abinavrockss en abinavrockss Wed, 29 Jul 2026 14:19:18 +0000 https://dev.to/abinavrockss/spec-driven-development-thoughts-39ak https://dev.to/abinavrockss/spec-driven-development-thoughts-39ak <p>Recently, I have been hearing about the new buzzword - Spec Driven Development. So, essentially, as Software Engineers - we are not allowed to touch the code directly anymore. Instead, we write these spec files which will combine both the business requirement with the technical limits and details to be fed as context to the AI agents. As of now, this proves to be somewhat useful in building new features from scratch, but sounds useless to bugs from existing features or small button changes. The token consumption also seems to be heavy as it takes up the context window and time to read the spec, come up with a plan, execute said plan and finish with the code (still, human eyes are needed after this part, cannot trust AI fully)</p> <p>I have been working with spec kit and Gemini's conductor (I know Gemini kind of sucks :( , just trying it out)</p> ai programming reviews