# Microsoft — The new primitives of agentic software delivery

- Company: Microsoft (microsoft.com)
- Announced: 2026-10-27T14:37:36+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://commandline.microsoft.com/new-agentic-software-delivery-primitives/
- Record: https://forck.live/items/28299-the-new-primitives-of-agentic-software-delivery
- Subject: Foundry / Responsible AI

Microsoft is describing the primitives of agentic software delivery, arguing that teams should transform the software lifecycle stage by stage rather than all at once. The company says the SDLC keeps its familiar loop of Plan, Build, Verify, Deploy and Observe, but each stage now draws on and contributes to a shared knowledge layer. Microsoft argues that ambitious teams who try to transform the entire SDLC at once tend to struggle, because when everything changes together it is hard to see what is working and what to fix. In its account, human attention moves to choosing problems, resolving ambiguity and judging whether the system built is the one intended, while agents take on more implementation and validation work. Each stage produces an artifact that carries the work forward, such as goals and acceptance criteria, a candidate implementation, or auditable evidence of system behavior. Microsoft says it is building these primitives into its developer products, citing Copilot taking an issue, spinning up a secure GitHub Actions environment, changing code, running validation and producing a draft PR for human review.

## Evidence

Verbatim from https://commandline.microsoft.com/new-agentic-software-delivery-primitives/:

> The promise of AI-first software development is extraordinary: describe what you want, and agents turn it into working software. But that framing treats the middle as a black box. Intent goes in, software comes out, and everything in between is assumed to simply be faster.
> 
> It isn’t that simple. Every stage of the software development lifecycle is changing, but not uniformly—some stages are transforming faster and earlier than others, and as capabilities improve, the bottlenecks move.
> 
> That’s why ambitious teams who try to transform the entire SDLC at once tend to struggle: when everything changes together, it’s hard to see what’s working, what’s failing, and what to fix. The problem is tractable, but only if we start with the primitives—the jobs to be done at each stage, the artifacts each stage produces, and the knowledge that connects them.
> 
> When we align on those primitives, the new software delivery system takes shape.
> 
> The jobs remain while the work changes
> 
> Software engineering has always required us to define goals, create software, validate and deliver it, and understand what happens when people use it.

---

Record: https://forck.live/items/28299-the-new-primitives-of-agentic-software-delivery
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md