New in Endora Commerce: a built-in CRM with sales opportunities See it →
Endora Commerce
May 2026 · 2 min read

Spec-Driven Development with AI: how we build B2B features

On Endora Commerce the specification takes most of our time. We brought this approach from more than 120 e‑commerce projects, where poorly described requirements turned out to be the most expensive part.

Michał Zabielski
Michał Zabielski
Founder and CEO, Endora

On Magento, Shopware and Sylius projects we kept seeing the same pattern: most rework did not come from bugs in the code but from requirements nobody had written down in full. That is why Endora Commerce has been built with Spec-Driven Development since its first module. AI tools speed up how we write tests, code and documentation, but direction, architecture and the final sign-off on every change stay with our engineers.

What Spec-Driven Development actually is

It is a way of working in which every feature starts as a written specification. The team describes its business, technical, architectural, performance and security aspects. Everything else is built from it:

  • Tests: acceptance criteria from the specification become executable checks.
  • Code: the implementation is built against the specification and its tests.
  • Documentation: the module description stays consistent with what actually runs.

The specification is an agreement between the business and the team. Implementation starts only once both sides have accepted it.

What does the specification of a single feature look like?

Usually a few pages: business context, user stories, acceptance criteria and notes on performance and security. The more precisely we describe edge cases, for example what happens when two pricing rules overlap, the fewer fixes show up at the testing stage.

We use the Spec-Kit toolkit to keep specifications in order. It helps break a specification into tasks and keeps the document structure consistent across the project, no matter who on the team works on a given module.

What does it mean for your rollout?

  • A predictable scope: before any code is written, you know exactly what will be built.
  • A faster start: a well-described feature goes from specification to a working module in 1-3 days, a larger one in about a week.
  • Documentation from day one: your team and any future partner know what was built and why.

Want to see how this method would work with your processes? Book a free consultation and we will walk through it using your platform as the example.

Selected modules explained on YouTube
Open the playlist →

Keep reading

Read the blog →