Design-first and Bugfix workflows add flexibility to Kiro’s spec-heavy model, but analysts are split on whether the changes will result in increased adoption.

InfoWorld is a source of news, analysis, and commentary on technology trends, IT strategies, and business innovation. With a focus on enterprise technology and digital transformation, InfoWorld offers insights and guidance for IT decision-makers, software developers, and technology professionals. From  articles on cloud computing and cybersecurity to product reviews and industry trends, InfoWorld helps readers navigate the complexities of modern IT environments and make informed decisions to drive business success.

InfoWorld

AWS is adding two new workflows to Kiro, its VS Code-based agentic IDE, to address the reality that most developers work on existing codebases rather than greenfield projects. The Design-first workflow lets developers start from an existing technical approach and have Kiro derive requirements and a task plan from it. The Bugfix workflow targets brownfield development, guiding engineers to document current vs. expected behavior before making code changes — turning debugging into a lightweight spec exercise. Analysts are divided: some see it as a pragmatic hybrid strategy to attract developers who prefer faster, conversational tools like Claude Code, Cursor, and GitHub Copilot, while others argue the changes still won't be enough to win over speed-focused developers. Enterprise and CIO audiences may find Kiro's structured approach more appealing for governance and auditability.

Kiro meets developers where they are, fixing bugs in existing projects