Skip to main content

I compared spec kit with and without extensions. Here is what I found

By

 This article is a continuation of my previous one, “Spec Kit to Delivery Discipline - A SDLC guide.” In that article, I looked at the Spec Kit from the perspective of the process and delivery disciplines. This time, I wanted to make a more practical comparison and really test the two approaches: Spec Kit alone versus Spec Kit with extensions.



So I ran the same experiment in both scenarios and compared the outputs side by side.
The experiment clearly showed that the version with extensions produced the better overall result.
The most interesting metrics are Halstead complexity metrics, which focus on how easily the code can be understood (cognitive effort) and the density of bug prediction. When using the extension to solve the same problem, the effort required to understand the code is almost 50% less. 
Both approaches produced a working solution, so the question was not only “does it work?” but also “which one gives a better engineering outcome?” Based on the results, the version with extensions came out ahead with a total weighted score of 9.00, compared to 7.19 for the base Spec Kit approach.
What is also interesting is where the difference appeared. The extension-based version was stronger in the areas that matter a lot in real delivery work: it had more tests, more documentation, and lower cognitive complexity, making the solution easier to understand and reason about. On the other hand, the base version performed slightly better on a few isolated code-quality checks, but not enough to change the overall picture.
The key takeaway: success means generating code that is complete, maintainable, and delivery-ready.
Extensions led to a more mature, usable result—better suited to real engineering needs.
If you are interested, I invite you to take a look at the repository and the comparison report. I shared the full outputs, methodology, and findings there so you can review everything yourself.
https://github.com/vunvulear/speckit-assessment 

Comments

Post a Comment

Popular posts from this blog

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

Why Database Modernization Matters for AI

By
  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...
Post a Comment
Read more

Azure Well-Architected AI workload Assessment

By
  AI is everywhere, part of the IT solutions we build and run today. Having an AI service, a good model, and data is not enough. As for cloud, the real difference is how we build, manage and run the whole solution. Microsoft created the Azure Well-Architected Framework for AI Workloads exactly for this reason — to help teams design AI systems that are reliable, secure, and cost-efficient. The assessment has six main categories that we cover in the next section. Based on the results, we can gain a good understanding of the current AI workload estate and a list of actions to improve how you run and manage your AI workloads . Designing the AI Application The first step in building your AI application is to consider how you will structure it. Using containers for tasks like data processing or model inference helps maintain consistency across the system. This approach makes it easier to update, move, and manage different components. When you have multiple steps in your workflow, such as...
Post a Comment
Read more