Spec-Driven Development: How AI Changes the Role of System Analyst in 2026

A systems analyst with over six years of experience, who has spent around three years working on products implementing LLM in business, analyzed the Spec-Driven Development (SDD) approach on Habr — a method in which specification becomes the central document, and AI uses it to implement the task.

Why analysts lack a unified approach

The author writes that he is categorically dissatisfied with the AI maturity of most colleagues on projects implementing AI in business. Part of the problem, in his view, is that systems analysts still lack a widely recognized approach to AI-enhancing their work — unlike developers, who have already formed such an approach. At the same time, job listings increasingly feature requirements like "experience with AI-native documentation" and "AI-centric analytics."

What is Spec-Driven Development

The author agrees with this market demand: if the expert in the code writing process today is a "developer plus AI" pair, then analytics pipeline needs to be adapted to such an expert. The logical solution is to write analytics immediately in text format, gradually moving away from visual tools like Miro and Draw.io.

At first, the author thought he had invented a new framework and even gave it a name — Analysis-as-Code. But it turned out that a similar approach already exists and is called Spec-Driven Development: in it, "specification" becomes the central document of the project, and AI uses it specifically when implementing the task.

• Author's experience — more than 6 years in systems analysis, around 3 years — on products implementing LLM in business
• Job listings increasingly require experience with "AI-native documentation" and "AI-centric analytics"
• The author's working name for the approach — Analysis-as-Code, but it turned out that 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 with an eye to the role of systems analysts in Russia and the CIS and tries to understand how this role changes with the transition to such an approach — instead of diagrams in Miro or Draw.io, the analyst works with text specification that AI reads and uses directly.

What this means

Spec-Driven Development captures what is already happening in practice: text specification becomes a common language between humans and AI tools, and the analyst's role shifts from drawing diagrams to writing structured, machine-readable requirements. For the labor market of the CIS, this means that "AI-native documentation" from a line in a job listing gradually transforms into a separate professional competency.