Amazon Web Services (AWS) is making updates to Kiro, its AI-powered development tool built into Visual Studio Code. Recognizing that most developers don’t work from scratch or follow strict processes, AWS is adding two new workflows designed to better fit real-world coding habits. These updates aim to help developers work more naturally, whether they’re fixing bugs or building on existing code.

New Workflows Focus on Real-World Coding Scenarios

Originally, Kiro was designed to guide developers through a process called spec-driven development (SDD), where they specify their goals upfront. But in practice, most developers start from an existing project, not a blank slate. Advait Patel, a site reliability engineer at Broadcom, explained that most developers work with messy code, bugs, or pre-approved designs. The new workflows acknowledge this reality and aim to make Kiro easier to use in these common situations.

The first new workflow is called Design-first. It allows developers to start from a technical idea they already have, like an architecture sketch or an implementation plan. Kiro then helps turn that initial thought into detailed requirements, a design specification, and a task list. Ankit Sharma, AWS’s senior product manager for agentic AI, shared in a blog post that this approach helps developers move from their existing ideas into a structured plan without starting from scratch.

Helping Developers Fix Bugs and Maintain Code

The second new workflow is called Bugfix. It’s aimed at developers working on existing codebases who want to improve or maintain their software. Instead of jumping straight into coding, this workflow guides them to document current behaviors, what the software should do, and what should stay unchanged. Sharma noted that this turns bug fixing into a lightweight specification exercise, making it more organized and less chaotic.

These updates are in response to feedback from Kiro users who liked the idea of structured specs but found the current process too rigid. The new workflows give developers more flexibility, allowing them to start with their ideas or existing code and then formalize their work in a way that feels natural.

Do These Changes Make Kiro More Appealing?

Some industry analysts see these updates as a way for AWS to stay competitive against other tools like Claude Code, Cursor, and GitHub Copilot. These rivals don’t enforce strict specifications and are popular because they are faster and easier to use. Stephanie Walter from HyperFrame Research explained that developer behavior often favors quick, conversational workflows over formal specs. The new Kiro workflows seem to be an attempt to blend structure with flexibility, making it more attractive for those who want some guidance but also need speed.

Walter described this as a hybrid approach—allowing developers to brainstorm first and formalize later, rather than forcing strict adherence to early specifications. However, some experts, like Dion Hinchcliffe from The Futurum Group, believe that these updates might not be enough to sway developers who prioritize speed. Patel echoed this sentiment, emphasizing that developers will adopt tools that save time overall, regardless of how structured they are.

While these new workflows aim to make Kiro more adaptable, ultimately, whether developers embrace them will depend on how much time they save and how well they fit into their existing routines. The updates show AWS’s recognition that flexibility and speed are key to attracting modern developers, but only time will tell if they succeed in making Kiro a go-to tool for everyday coding tasks.

Inspired by

• https://www.infoworld.com/article/4135310/aws-adds-design-first-and-bugfix-workflows-to-kiro.html

Sources

• kiro.dev