# Is the future of AI development spec-driven? | LinearB Blog

> Amit Patel, Director of Software Development for AWS Kiro, explains why spec-driven development is the future of AI development, solving the context loss problem by creating a structured, persistent three-stage spec (requirements, design, and tasks) that acts as the agent's long-term memory.

_This is a markdown rendering of a live HTML page on linearb.io, generated for AI/LLM consumption — it is not a markdown-only site. To get the full HTML page instead, request this URL with an explicit `Accept: text/html` header (no wildcard, no markdown preference)._


```json
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://linearb.io/"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Blog",
      "item": "https://linearb.io/blog"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Is the future of AI development spec-driven?",
      "item": "https://linearb.io/blog/future-of-ai-development-spec-driven-aws-kiro"
    }
  ]
}
```

[Home](https://linearb.io/)

/

[Blog](https://linearb.io/blog)

/

Is the future of AI development spec-driven?

# Is the future of AI development spec-driven?

![Photo of Andrew Zigler](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Headshot3_d7231cbda7?_a=BAVMn6ID0)

By [Andrew Zigler](https://linearb.io/blog/future-of-ai-development-spec-driven-aws-kiro#andrew-zigler)

|

November 14, 2025

![Blog_Agentic_IDE_2400x1256_f05088e798](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_Agentic_IDE_2400x1256_f05088e798?_a=BAVMn6ID0)

## **Is the future of AI development spec-driven?**

Every developer who has used an AI assistant knows the frustration of its limited memory. While chat-based tools are effective for simple, single-file tasks, they struggle with complex, multi-day projects. As [Amit Patel](https://linearb.io/dev-interrupted/podcast/spec-driven-development-aws-kiro), Director of Software Development at AWS, notes, "It becomes quite difficult to have enough context and enough memory... to remember what you did yesterday or two days ago... sometimes I forget what I told the agent to do three hours ago!"

This "amnesia problem" was the genesis for an agentic IDE built by his team at Amazon, which has quickly grown a vibrant internal community. Instead of an ephemeral chat, this new tool is built on the concept of "spec-driven development"—a formal structure that gives the AI persistent context and a clear plan.

This article explores this innovative approach, from its three-stage spec and structured task list to the developer-centric ergonomics that make it work, all built through a deeply iterative, community-driven process.

## **Spec-driven development: giving AI a plan and a memory**

At the heart of this new approach is "spec-driven development," a formal, three-stage process that mirrors traditional software best practices. "Rather than remembering what the prompts were three days ago," Patel explains, "we're saying is... \[we\] will allow you to essentially build a plan, a structure for your project." This spec becomes the persistent "memory" [that guides the AI agent](https://linearb.io/blog/how-agentic-ai-will-disrupt-your-software-delivery-lifecycle).

The spec consists of three simple stages: requirements, design, and a task list. This framework provides just enough structure to keep the AI on track, which is key because, as Patel notes, "The less ambiguity you give it, the better the output will be." Developers can iterate on this spec (which is stored in Markdown) via chat or direct editing, preserving traditional workflows while radically accelerating them. This process doesn't circumvent best practices like design reviews; it enhances them. "Typically... it would take an engineer maybe 2, 3, 4 days to write a design doc," Patel says. "The benefit... is that you get the design doc in, you know, 10, 15 minutes and then you can just go and have that meeting."

The most powerful part of this model is the structured task list, which gives the AI its power for complex, multi-day projects. The task list provides a clear, persistent record of completed and remaining work, allowing a developer to step away for days and return, picking up exactly where they left off. Because the AI can see the full requirements, design, and which tasks are done, all of that context is available for the next step. The team validates this approach by "dogfooding" their own product to build new features, including for large-scale production projects like S3 components, proving its ability to handle mission-critical development.

## **A human-centered process: ergonomics and iteration**

Building an intuitive and productive tool was a journey in itself, requiring "six attempts to get there," Patel acknowledges. [This relentless focus on developer ergonomics](https://linearb.io/blog/developer-experience) was crucial for balancing the need for structure with the flexibility that different workflows require.

A perfect example of this human-centered design came directly from user feedback. An early tester noted that the agent could take 5-10 minutes to execute a complex task and they didn't want to "keep watching it do its work." They asked for a notification system. The team took this feedback and, in a powerful display of dogfooding, used the tool itself to build the notification system—completing in two days what they had estimated would take three to four weeks.

This focus on accessibility also guided key product decisions. The team made a "larger, more meaningful decision" to allow logins via Gmail rather than requiring an AWS account. This small change dramatically lowered the barrier to entry, making the tool accessible to all developers, not just those already deep in the AWS ecosystem.

This successful process was [driven by a direct feedback loop](https://linearb.io/blog/the-cornerstone-of-software-quality-and-efficiency-cycle-time). The team set up a Slack channel with its first 100 adopters, giving them nightly builds and, crucially, the time and space to engage. "We didn't cram the engineer's days with task after task," Patel shares. "We actually allowed them to be on Slack, engage with the customers... and get their inputs." This direct engagement, which expanded to include solution architects and other roles, allowed the team to filter feedback and build a tool developers genuinely wanted to use.

## **The future of AI is structured**

The journey of building this agentic IDE highlights a fundamental truth for the next wave of AI development: a conversational chat interface is not enough. To tackle complex, real-world projects, AI needs what developers have always needed: a plan, a memory, and a clear set of tasks.

Amit Patel and his team at AWS have shown that by embedding traditional software discipline—requirements, design, and task lists—directly into the AI's core, we can solve its context problem. This "spec-driven" approach doesn't replace [engineering best practices](https://linearb.io/resources/8-habits-of-highly-productive-eng-teams); it accelerates them, turning a four-day design doc process into a 15-minute review.

By focusing on developer ergonomics and building in lockstep with their community, Patel's team has built more than just a faster tool. They've built a more resilient, context-aware partner, offering a glimpse into a future where AI augments our own structured thinking rather than just reacting to our last prompt.

For the full story on building a structured, agentic IDE, listen to Amit Patel discuss these ideas in depth on the Dev Interrupted podcast.

## Improve developer productivity with LinearB

Find us on

[](https://www.linkedin.com/company/linearb)
[](https://devinterrupted.substack.com/)

![Headshot3_d7231cbda7](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Headshot3_d7231cbda7?_a=BAVMn6ID0)

## Andrew Zigler

Andrew Zigler is a GTM Engineer at LinearB and the host of Dev Interrupted, a twice-weekly podcast and newsletter where 40k+ builders decode the transition to AI-native development and agentic orchestration. A classicist by training with a degree from The University of Texas at Austin, Andrew spent his early career teaching in Japan before channeling his interdisciplinary instincts into the tech world. His polymath background informs everything he builds, from automated workflows to the stories he tells about the seismic shifts reshaping software creation.

### Connect with

[](https://www.linkedin.com/in/andrewzigler)
[](https://substack.com/@zigler)
[](https://x.com/andrewzigler)

## Your next read

[![Cover image for Rippling's employee graph turns HR data into an agentic AI platform](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_Post_Name_2400x1256_be5ec4183f?_a=BAVMn6ID0)](https://linearb.io/blog/rippling-albert-strasheim-employee-graph-agentic-ai)

AI

[Rippling's employee graph turns HR data into an agentic AI platform](https://linearb.io/blog/rippling-albert-strasheim-employee-graph-agentic-ai)

Rippling CTO Albert Strasheim explains why the employee graph serves as the essential context layer for enterprise agentic AI. Discover how unifying HR, IT,...

[![Cover image for Deterministic guardrails must evolve to control probabilistic AI systems](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_Post_Name_2400x1256_5_f5375661ec?_a=BAVMn6ID0)](https://linearb.io/blog/launchdarkly-cameron-etezadi-deterministic-guardrails-probabilistic-ai-darkfactory)

AI

[Deterministic guardrails must evolve to control probabilistic AI systems](https://linearb.io/blog/launchdarkly-cameron-etezadi-deterministic-guardrails-probabilistic-ai-darkfactory)

LaunchDarkly CTO Cameron Etezadi explains why traditional engineering pipelines are breaking down in a probabilistic, AI-driven world. Discover how to safely...

[![Cover image for Slack turns channels into the context engine for agentic AI](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_Post_Name_2400x1256_077524ba8b?_a=BAVMn6ID0)](https://linearb.io/blog/slack-jaime-delanghe-mcp-agent-context-channels)

AI

[Slack turns channels into the context engine for agentic AI](https://linearb.io/blog/slack-jaime-delanghe-mcp-agent-context-channels)

Slack Chief Product Officer Jaime DeLanghe breaks down how channels serve as the foundational context layer for human-agent collaboration. Learn why Slack is...

## Structured data

_Machine-readable metadata (JSON-LD) embedded in the page for search/AI context — not content rendered on the page itself._

```json
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "LinearB",
  "url": "https://linearb.io/",
  "logo": "https://assets.linearb.io/image/upload/v1715628027/logo-mark-lg.svg",
  "description": "LinearB is the engineering productivity platform that helps engineering leaders prove AI is improving throughput without sacrificing delivery confidence, flow efficiency, or developer experience.",
  "sameAs": [
    "https://www.linkedin.com/company/linearb"
  ],
  "award": [
    {
      "@type": "Award",
      "name": "LinearB is a Leader in the 2026 Gartner® Magic Quadrant™ for Developer Productivity Insight Platforms",
      "dateAwarded": "2026",
      "awardedBy": {
        "@type": "Organization",
        "name": "Gartner®"
      }
    },
    {
      "@type": "Award",
      "name": "Great Place to Work Certification",
      "dateAwarded": "2025-2027",
      "awardedBy": {
        "@type": "Organization",
        "name": "Great Place to Work"
      }
    },
    {
      "@type": "Award",
      "name": "America's Best Startup Employers 2025",
      "dateAwarded": "2025",
      "awardedBy": {
        "@type": "Organization",
        "name": "Forbes Magazine"
      }
    }
  ],
  "hasCertification": [
    {
      "@type": "Certification",
      "name": "SOC 1 Type 2"
    },
    {
      "@type": "Certification",
      "name": "SOC 2 Type 2"
    },
    {
      "@type": "Certification",
      "name": "GDPR Compliance certification"
    },
    {
      "@type": "Certification",
      "name": "ISO 27001"
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Is the future of AI development spec-driven?",
  "url": "https://linearb.io/blog/future-of-ai-development-spec-driven-aws-kiro",
  "author": {
    "@type": "Person",
    "name": "Andrew Zigler"
  },
  "datePublished": "2025-11-14T08:00:00.000Z",
  "dateModified": "2025-11-14T08:00:00.000Z",
  "image": "https://assets.linearb.io/image/upload/v1763101690/Blog_Agentic_IDE_2400x1256_f05088e798.png",
  "publisher": {
    "@type": "Organization",
    "name": "LinearB",
    "logo": "https://assets.linearb.io/image/upload/v1777485755/linearb-logo-2026.png"
  },
  "description": "Amit Patel, Director of Software Development for AWS Kiro, explains why spec-driven development is the future of AI development, solving the context loss problem by creating a structured, persistent three-stage spec (requirements, design, and tasks) that acts as the agent's long-term memory."
}
```

## More on linearb.io

### Top navigation

- [Book a Demo](https://linearb.io/book-a-demo)
- [AI Code Reviews — Catch security risks, bugs, and spec mismatches](https://linearb.io/platform/ai-code-reviews)
- [AI & Productivity Insights — See how AI tools affect cycle time and delivery speed](https://linearb.io/platform/ai-developer-productivity-insights)
- [Measure AI Impact — Track AI adoption and tie it to delivery outcomes](https://linearb.io/use-case/measure-ai-impact)
- [MCP Server — Chat with your data to spot patterns and boost output](https://linearb.io/platform/mcp-server)
- [Resource Allocation — Cost initiatives and shape your investment strategy](https://linearb.io/platform/resource-allocation)
- [Cost Capitalization — Capitalize engineering costs with audit-ready reports](https://linearb.io/platform/cost-capitalization)
- [Dev Team Management — Set targets and tie throughput to business outcomes](https://linearb.io/platform/goals-and-reporting)
- [DevOps Workflow Automation — Policy-based PR routing, approvals, and tests](https://linearb.io/platform/ai-workflow-governance)
- [AI Powered Support — Unify AI and human code delivery in one clear view](https://linearb.io/use-case/ai-powered-support)
- [Optimization — Surface friction with feedback and MCP insights](https://linearb.io/platform/developer-experience)
- [Reporting — Spot what's working and what needs attention](https://linearb.io/use-case/measuring-developer-experience)
- [Surveys — Turn developer feedback into actionable signals](https://linearb.io/platform/developer-surveys)
- [Platform overview](https://linearb.io/platform/overview)
- [Register now](https://linearb.io/event/engineering-productivity-gap)
- [Customers](https://linearb.io/customers)
- [Pricing](https://linearb.io/pricing)
- [Why choose LinearB — Explore your data. Measure performance. Act to improve it.](https://linearb.io/why-linearb)
- [APEX framework — The operating model for AI-era engineering teams](https://linearb.io/resources/apex-framework)
- [Anti-FAQ — The questions other vendors won't answer](https://linearb.io/why-linearb/anti-faq)
- [Security — Enterprise-grade compliance and zero code access](https://linearb.io/security)
- [Build vs. buy — The hidden cost of building it yourself](https://linearb.io/resources/build-vs-buy)
- [Dev Interrupted Podcast — Conversations with engineering leaders](https://linearb.io/dev-interrupted/podcasts)
- [Reports & Guides — Deep dives on productivity and delivery](https://linearb.io/resources)
- [Webinars — Expert sessions on productivity and AI](https://linearb.io/resources?category=workshops)
- [Metrics Benchmarks — See how your engineering org stacks up](https://linearb.io/resources/software-engineering-benchmarks-report)
- [Blog — Product updates and practical insights](https://linearb.io/blog)
- [Help Center — Documentation, setup, and support](https://linearb.helpdocs.io)
- [API Docs](https://docs.linearb.io/api-overview)
- [Status](https://www.linearbstatus.com/)
- [Integrations](https://linearb.io/integrations)
- [LinearB Library](https://linearb.io/library)
- [Engineering metrics](https://linearb.io/library/engineering-metrics)
- [Platform engineering](https://linearb.io/library/platform-engineering)
- [Engineering glossary](https://linearb.io/library/engineering-glossary)
- [Developer productivity](https://linearb.io/library/developer-productivity)
- [AI in software development](https://linearb.io/library/ai-in-software-development)
- [Engineering management](https://linearb.io/library/engineering-management)
- [Developer experience](https://linearb.io/library/developer-experience)
- [DevOps](https://linearb.io/library/devops)
- [Engineering operations and the context layer](https://linearb.io/library/engineering-operations)
- [Engineering efficiency](https://linearb.io/library/engineering-efficiency)
- [Software delivery](https://linearb.io/library/software-delivery)
- [Research and data](https://linearb.io/library/engineering-benchmarks-and-research)
- [LinearB is a Leader in the 2026 Gartner® Magic Quadrant™ for Developer Productivity Insight Platforms](https://linearb.io/resources/gartner-magic-quadrant-dpi-platforms-2026)
- [Sign in](https://app.linearb.io/login)
- [Enterprise](https://linearb.io/solutions/enterprise)
- [Contact](https://linearb.io/contact-us)
- [About us](https://linearb.io/about-us)
- [Careers](https://linearb.io/careers)
- [Service agreement](https://linearb.io/services-agreement)
- [Privacy policy](https://linearb.io/privacy-policy)
- [DPA](https://linearb.io/data-processing-agreement)
- [Security FAQ](https://linearb.io/security-faq)
- [Substack](https://devinterrupted.substack.com/)

### Footer

_Additional links from the site footer, not repeated from the top navigation above._

- [GitHub](https://github.com/linear-b)
- [LinkedIn](https://www.linkedin.com/company/linearb)
- [Twitter](https://twitter.com/LinearB_Inc)