Spec-Driven Development: How AI Is Changing the Systems Analyst's Role in 2026

A systems analyst with more than six years of experience, who has spent about three years on products that bring LLMs into business, has written up the Spec-Driven Development (SDD) approach on Habr. It is a method in which the specification becomes the central document, and AI uses it to carry out the task.

Why analysts lack a common approach

The author writes that he is thoroughly dissatisfied with the AI maturity of most of his colleagues on projects that bring AI into business. In his view, part of the problem is that systems analysts still have no widely accepted approach to AI-augmenting their work, unlike developers, who have already settled on one. Meanwhile, job listings increasingly include requirements such as "experience writing AI-native documentation" and "AI-centric analytics."

What is Spec-Driven Development

The author agrees with this market demand: since the expert writing code today is a "developer plus AI" pairing, the analytics pipeline should be adapted to that expert. The logical solution is to write analytics directly in a text format, gradually moving away from visual tools such as Miro and Draw.io.

At first, the author thought he had come up with a new framework and even gave it a name: Analysis-as-Code. It turned out, however, that a similar approach already exists and is called Spec-Driven Development: the "specification" becomes the project's central document, and AI uses it when carrying out the task.

• The author has more than 6 years in systems analysis, about 3 of them on products that bring LLMs into business
• Job listings increasingly ask for experience with "AI-native documentation" and "AI-centric analytics"
• The author's working name for the approach was Analysis-as-Code, but it turned out the term Spec-Driven Development (SDD) already exists
• The article examines SDD in relation to the role of systems analysts in Russia and the CIS

In the article, the author examines Spec-Driven Development specifically with the role of systems analysts in Russia and the CIS in mind, and tries to work out how that role changes under this approach: instead of diagrams in Miro or Draw.io, the analyst works with a text specification that AI reads and uses directly.

What this means

Spec-Driven Development codifies what is already happening in practice: the text specification is becoming a shared language between humans and AI tools, and the analyst's role is shifting from drawing diagrams to writing structured, machine-readable requirements. For the CIS job market, this means "AI-native documentation" is gradually moving from a line in a job listing to a distinct professional skill.