Kiro's spec-driven development: how AI-generated code enters engineering
An InfoQ Chinese analysis traces Amazon Web Services' Kiro and its spec-driven development approach: Kiro's July 16, 2025 preview used a three-part Specs workflow (requirements.md, design.md, tasks.md) to constrain AI-generated code, with Specs kept in two-way sync with the codebase. The article says Kiro's November 18, 2025 general availability added property-based testing (PBT), checkpoints and a Kiro CLI team subscription, and that February 2026 brought design-first and bug-fix workflows, which the piece reads as an acknowledgment that most developers do not start from scratch. Kiro Crew, open-sourced on August 4, 2026, is described as a continuously running multi-agent workspace built on Kiro CLI, with the vendor claiming seven layers of security protection; the article also promotes a Kiro ideas event.
The article argues the competitive question for AI coding tools has shifted from whether code can be generated to whether it can enter the engineering system, with Kiro's Spec, PBT, Hooks and Steering offered as one auditable approach.
AI 编程工具的竞争，在过去一年里换了个赛道。
2025 年上半年，话题还集中在"能不能生成"——模型能不能写出可编译的代码，能不能一次跑通一个完整功能。到 2025 年下半年，Cursor、GitHub Copilot、Codex CLI、Gemini CLI 以及 Kiro CLI 先后把 Agent 推进终端之后，生成能力本身已经很难再构成差异点。
真正的问题后移了：AI 写出来的代码，能不能进工程体系。
亚马逊云科技在 2025 年 7 月 16 日第一次推出 Kiro 预览版时，给出的答案是 spec-driven development（规范驱动开发）。一年多过去，这套方法论经历了正式可用、工作流修正、以及向多 Agent 工作区的延伸。它解决的到底是什么，边界又在哪里，我们一篇文章讲清楚。
#Kiro#Amazon Web Services#Kiro CLI#Kiro Crew#Cursor#GitHub Copilot#Claude Sonnet 4.5#Claude Haiku 4.5#Codex CLI#Gemini CLI