Skip to main content

ame Prompt, Three Workflows: What Happens When BMAD Joins SpecKit

By

 In my previous article, I looked at SpecKit without extensions and SpecKit with extensions, trying to understand how much structure really helps when we use AI to generate code. This post is a follow-up of that work. I kept the same prompt, tools, and evaluation method, but added a third approach: BMAD (BMad Agentic Development).

From the beginning, BMAD felt different. SpecKit guides the AI through clear workflows. BMAD, on the other hand, feels like a small virtual team that thinks first, plans more, and then writes code. This difference shows clearly in the output.

What impressed me most was simplicity. Even if BMAD did not win on all linting scores, the code was much easier to read and reason about. The Halstead cognitive metrics showed a big gap that classic linters do not really capture. In simple words, the BMAD code is easier for a human brain.

Testing was another strong signal. BMAD produced the highest number of tests and almost 99% coverage, while also having the smallest codebase. Less code, more tests — that is usually a good sign.

Still, SpecKit with extensions remains very strong for documentation and project maturity. If you think about long‑term maintenance or enterprise readiness, extensions add real value.

Below is a small snapshot of the numbers that influenced my conclusion:

Metric

SpecKit

SpecKit + Extensions

BMAD

Source Lines of Code

604

629

517

Pylint Score

9.68

9.32

8.50

Halstead Effort

2,665

1,526

1,090

Test Count

65

102

107

Test Coverage

94.27%

92.24%

99.01%

 

My takeaway so far is simple:
BMAD optimises for thinking and simplicity, while SpecKit + Extensions optimises for structure and completeness.
Ultimately, establishing a balance between BMAD and SpecKit + Extensions is key. Measuring the trade-offs helps determine the optimal approach for your needs.


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 Service Bus - How to extend the lock of a message | RenewLock

By
In this post we will discuss about Azure Service Bus Topics and Queues, with a special focus on Peek and Lock feature. Introduction Azure Service Bus is a messaging system that allows us to send messages between different systems in a reliable and easy way. A lot of concepts from ESB are implemented by Service Bus, allowing us to do do magic stuff with messages. There are two ways to consume messages from Service Bus Peek and Lock - locks a message for a specific time internal and notify Service Bus when we want to mark the message as processed (removed from Service Bus) Receive and Delete  - once a message is received from Service Bus, it is also deleted automatically from the messaging system Peek and Lock When using Peek and Lock, by default we lock the message for 60 seconds. This means that in this time interval the message is not available/visible for other consumers. Once we process the message we can mark it as processed. If we don't mark the message as processe...
Post a Comment
Read more