<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/adlc-the-lifecycle-taking-shape-napaas7zg" -->

---
title: ADLC: The Lifecycle Taking Shape | daily.dev
description: An essay proposes a lifecycle model for AI-agent-driven software development, arguing that classic SDLC diagrams break down once agents execute tasks in...
canonical: https://daily.dev/posts/adlc-the-lifecycle-taking-shape-napaas7zg
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: ADLC: The Lifecycle Taking Shape | daily.dev
og:description: An essay proposes a lifecycle model for AI-agent-driven software development, arguing that classic SDLC diagrams break down once agents execute tasks in...
og:url: https://daily.dev/posts/adlc-the-lifecycle-taking-shape-napaas7zg
og:image: https://api.daily.dev/og/posts/NApaaS7Zg.png
og:image:alt: ADLC: The Lifecycle Taking Shape
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# ADLC: The Lifecycle Taking Shape

**[Medium](https://daily.dev/sources/medium_js)** · 15 min read · 0 upvotes · 0 comments

## Summary

An essay proposes a lifecycle model for AI-agent-driven software development, arguing that classic SDLC diagrams break down once agents execute tasks in minutes instead of days. It sketches a five-stage, two-lane model where agents handle planning, generation and evidence collection while humans retain control over intent, validation and outcomes. Specifications and evaluation sets become the durable artifacts worth maintaining, replacing code as the thing that used to survive between releases. The piece maps this abstract lifecycle onto AWS's AI-Driven Development Lifecycle (AI-DLC, published July 2025) and onto Explyt, a JetBrains IDE agent the author works on, showing how features like Plan mode, Edit Scope, Auto Review and Debug mode correspond to lifecycle stages. It closes with a set of questions engineering leads can use to audit whether their own process has these artifacts in place.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://medium.com/@explyt.ai/adlc-the-lifecycle-taking-shape-77437ca2e201>

## Questions this post answers

### What are the three phases of AWS's AI-Driven Development Lifecycle (AI-DLC)?

AI-DLC has three phases: Inception, where AI transforms business intent into requirements and stories through 'Mob Elaboration' with team validation; Construction, where AI proposes architecture, domain models, code, and tests through 'Mob Construction' with real-time team clarification; and Operations, where AI manages infrastructure as code and deployments with team oversight. It was described by Raja SP on the AWS DevOps blog on 31 July 2025.

_Teams weighing structured AI development workflows can follow AI-DLC coverage and comparisons on daily.dev._

### What does AI-DLC mean by replacing sprints with bolts?

Bolts are shorter, more intense work cycles measured in hours or days rather than weeks, replacing traditional two-week sprints, with epics replaced by units of work. The shift happens because sprint ceremonies like planning, review, and retrospectives exist to protect a human implementation window that no longer applies once agents complete work in hours; validation must instead be automated per bolt via an eval set.

_Anyone restructuring team cadence around AI-assisted delivery can track these workflow shifts on daily.dev._

### Why do specifications and test suites become more important than code in agent-driven development?

Code becomes cheap and regenerable once agents write it quickly, so the specification (the input every regeneration is planned against) and the evaluation set (the test suite that accepts or rejects a regeneration) become the artifacts that must stay correct and maintained, while code becomes disposable. A change record tying spec, change, and evidence together makes the process auditable.

_Developers rethinking what to maintain as code generation gets cheaper can follow this shift on daily.dev._

## Similar posts on daily.dev

- [The AI-Driven SDLC: From Prompting to Process](https://daily.dev/posts/the-ai-driven-sdlc-from-prompting-to-process-bkszru6ln) · Medium · 0 upvotes · 0 comments
- [Your agent context needs a development lifecycle](https://daily.dev/posts/your-agent-context-needs-a-development-lifecycle-vacgztkaf) · The New Stack · 0 upvotes · 1 comments
- [The AI SDLC transformation playbook](https://daily.dev/posts/the-ai-sdlc-transformation-playbook-hykxezayi) · Atlassian · 1 upvotes · 0 comments
- [Building with AI-DLC using Amazon Q Developer](https://daily.dev/posts/building-with-ai-dlc-using-amazon-q-developer-cos9ebjy7) · AWS · 1 upvotes · 0 comments

---

Tags: [#testing](https://daily.dev/tags/testing), [#ai-coding](https://daily.dev/tags/ai-coding), [#jetbrains](https://daily.dev/tags/jetbrains)

[View this post on daily.dev](https://daily.dev/posts/adlc-the-lifecycle-taking-shape-napaas7zg)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"ADLC: The Lifecycle Taking Shape","url":"https://daily.dev/posts/adlc-the-lifecycle-taking-shape-napaas7zg","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/adlc-the-lifecycle-taking-shape-napaas7zg"},"datePublished":"2026-09-05T19:29:20.998Z","dateModified":"2026-09-13T18:58:34.404Z","description":"An essay proposes a lifecycle model for AI-agent-driven software development, arguing that classic SDLC diagrams break down once agents execute tasks in...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b722776b0066c9ca6e5a3851b5332245?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b722776b0066c9ca6e5a3851b5332245?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Medium","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Medium","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/medium","url":"https://daily.dev/sources/medium_js"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/adlc-the-lifecycle-taking-shape-napaas7zg","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"testing,ai-coding,jetbrains","timeRequired":"PT15M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Medium","item":"https://daily.dev/sources/medium_js"},{"@type":"ListItem","position":3,"name":"ADLC: The Lifecycle Taking Shape"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/adlc-the-lifecycle-taking-shape-napaas7zg#faq","mainEntity":[{"@type":"Question","name":"What are the three phases of AWS's AI-Driven Development Lifecycle (AI-DLC)?","acceptedAnswer":{"@type":"Answer","text":"AI-DLC has three phases: Inception, where AI transforms business intent into requirements and stories through 'Mob Elaboration' with team validation; Construction, where AI proposes architecture, domain models, code, and tests through 'Mob Construction' with real-time team clarification; and Operations, where AI manages infrastructure as code and deployments with team oversight. It was described by Raja SP on the AWS DevOps blog on 31 July 2025. Teams weighing structured AI development workflows can follow AI-DLC coverage and comparisons on daily.dev."}},{"@type":"Question","name":"What does AI-DLC mean by replacing sprints with bolts?","acceptedAnswer":{"@type":"Answer","text":"Bolts are shorter, more intense work cycles measured in hours or days rather than weeks, replacing traditional two-week sprints, with epics replaced by units of work. The shift happens because sprint ceremonies like planning, review, and retrospectives exist to protect a human implementation window that no longer applies once agents complete work in hours; validation must instead be automated per bolt via an eval set. Anyone restructuring team cadence around AI-assisted delivery can track these workflow shifts on daily.dev."}},{"@type":"Question","name":"Why do specifications and test suites become more important than code in agent-driven development?","acceptedAnswer":{"@type":"Answer","text":"Code becomes cheap and regenerable once agents write it quickly, so the specification (the input every regeneration is planned against) and the evaluation set (the test suite that accepts or rejects a regeneration) become the artifacts that must stay correct and maintained, while code becomes disposable. A change record tying spec, change, and evidence together makes the process auditable. Developers rethinking what to maintain as code generation gets cheaper can follow this shift on daily.dev."}}]}
```

