Spec Kit to Delivery Discipline

Spec Kit to Delivery Discipline - A SDLC guide

If we already accept that Spec Kit is a valuable foundation, the more important conversation is how to use its extension ecosystem in a disciplined way. In my view, the real opportunity is not in adding more tooling. It lies in forming a delivery model where each extension has a clear purpose across the lifecycle. The overall stack should strengthen control, traceability, and delivery confidence.

For a standard enterprise-oriented setup, I see the most effective combination as the following (for March 2026):

Requirements / Discovery	DocGuard	Improves specification quality, structure, and traceability
Planning / Backlog	Jira Integration	Connects requirements and task breakdowns to the delivery management tool
Verification / Validation	Verify	Validates implementation against the specification
Verification / Delivery Control	Verify Tasks	Detects tasks marked as complete without actual implementation
Maintenance / Drift Control	Spec Sync	Keeps specification and implementation aligned over time

What makes this stack strong is not exclusively the quality of the individual extensions, but also the fact that, together, they create a practical control system across the SDLC. They help establish stronger specification discipline at the start, better execution alignment during delivery, and more robust integrity checks once implementation is underway. From a leadership perspective, this is where the real value sits: not in automation for its own sake, but in using the right extensions to create a more reliable, transparent, and scalable engineering model.

At the same time, teams need to be careful not to confuse capability with maturity. One of the biggest risks in this space is extension overlap. When multiple extensions start covering similar stages, introducing similar controls, or creating competing views of progress, the result is not better governance. The result is ambiguity. The same principle applies more broadly: the objective should always be a curated stack with clear responsibilities, not an accumulation of features.

If stronger lifecycle control is required, I would particularly highlight the Fleet Orchestrator extension. From my perspective, this is the extension that best reflects the direction many enterprise delivery models need to take. It supports stage-by-stage progression, explicit review points, and, importantly, a human-in-the-loop approach. That matters because the future of software delivery will not be defined by removing people from the process, but by placing them at the right decision points while allowing the tooling to improve speed, structure, and consistency around them. Fleet Orchestrator is therefore not simply another extension; it is a strong enabler for organisations that want more deliberate control and higher confidence as work moves from one phase to another.

My recommendation is to start with a disciplined standard extension stack: DocGuard, an ALM integration, Verify, Verify Tasks, and Spec Sync. This combination offers comprehensive SDLC coverage and balances quality, control, and simplicity. If the delivery environment requires additional checkpoints, governance, or executive visibility, introduce Fleet Orchestrator as the next step.

The strategic point is simple: successful adoption will not come from using the most extensions. It will come by choosing the few that reinforce clarity, accountability, and controlled progress across the lifecycle. That is the mindset required if we want Spec Kit to evolve from an interesting framework into a disciplined enterprise delivery capability.

How to audit an Azure Cosmos DB

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...

Why Database Modernization Matters for AI

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...

Azure Well-Architected AI workload Assessment

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...

Cloud as a Story - Vunvulea Radu

Search This Blog