Kiro's three-stage requirements analysis pipeline: refinement, auto-formalization, and logical analysis using an SMT solver Image: kiro.dev
by VibecodedThis

Amazon Q Developer Is Retiring. AWS's Replacement Is Kiro.

AWS announced it is ending support for Amazon Q Developer IDE plugins and paid subscriptions on April 30, 2027. New signups stop May 15. On the same day, Kiro — the replacement — shipped three major spec features: neurosymbolic requirements analysis, parallel task execution, and Quick Plan mode.

Share

AWS published the end-of-support timeline for Amazon Q Developer on May 12: IDE plugins and paid subscriptions reach end of life on April 30, 2027. New signups for the free tier and paid plans are blocked starting May 15, 2026 — two days from today.

The replacement is Kiro.

What’s Going Away

The deprecation covers Q Developer IDE plugins across VS Code, JetBrains, Eclipse, and Visual Studio, and all paid subscriptions. Existing subscribers can keep using the plugins through April 30, 2027 and can continue adding new users until May 15.

Q Developer isn’t disappearing entirely. It stays available inside the AWS Management Console, the AWS documentation site, and integrations for Slack and Microsoft Teams. AWS simply isn’t building out the IDE-facing developer product anymore.

“Amazon Q Developer IDE plugins and paid Subscriptions will reach end of support on April 30, 2027,” the announcement reads, “giving customers 12 months to transition to Kiro.”

What Kiro Is

Kiro is AWS’s take on what a coding tool should be in an era where agents write most of the code. The core idea is spec-driven development: before any code runs, you define requirements, design, and tasks in structured files that the agent can reason about and re-read as context.

The product ships as both an IDE and a CLI. It includes inline chat, terminal integration, and MCP server support. The latest AI models are available on Kiro; AWS confirmed the newest versions are exclusive to Kiro going forward.

Three New Features Shipped May 12

On the same day as the Q Developer deprecation notice, Kiro shipped IDE 0.12.155 with three meaningful additions.

Requirements Analysis

The headline feature uses what Kiro calls neurosymbolic AI: a combination of LLMs and a formal SMT (Satisfiability Modulo Theories) solver to check requirements for logical problems before a single line of code is written.

The pipeline has three stages. First, the LLM rewrites vague requirement language into testable EARS-notation criteria (“WHEN … THE SYSTEM SHALL …”). Second, those criteria get translated into formal logical assertions. Third, an SMT solver checks the assertion set for contradictions, completeness gaps, and ambiguities that different developers might interpret differently.

The practical result: if requirement R2 says “backorder unavailable inventory” and requirement R3 says “never backorder,” the solver flags that as a mathematical impossibility rather than letting it surface as a bug in production.

Kiro cites research finding that underspecified prompts are twice as likely to regress across model versions, with LLMs silently filling in gaps in ways the original author didn’t intend.

Parallel Task Execution

Kiro now builds a dependency graph from the task list inside a spec and runs independent tasks concurrently. Tasks that write to the same files or test code from earlier tasks still run in sequence. Everything else runs in parallel.

AWS says this brings implementation time for large specs from over an hour down to about 15 minutes, a reduction of roughly 75%.

Quick Plan Mode

The standard spec workflow requires approving requirements, then design, then tasks one phase at a time. Quick Plan skips that. You answer a few clarifying questions upfront, Kiro scans your workspace for language and framework context, and then it generates requirements, design, and tasks in one pass.

If you change just the tasks layer, only tasks regenerate. Adjusting the design layer triggers design and tasks. Scope changes restart the full pipeline.

Amazon Q Developer has been around since 2023. It never found strong adoption against GitHub Copilot, and the developer focus was always diffuse, split between IDE features and a broader AWS assistant play. Kiro is more focused. Whether it can catch up to Cursor, Windsurf, and Claude Code in the IDE market is a different question — but AWS is clearly done trying to maintain both.

Sources:

Share