Kiro

(3/3) And then there's the Bugfix Spec 🐛 What makes this different is the three section it looks at: what's broken, what the fix looks like, and, this is the important one, what must NOT change. Kiro generates property-based tests for all three. Proves the bug exists, proves the fix works, and proves nothing else broke. Thank you Kiro 😍 Surgical. I like it. If you want to read more on these new specs check out the blog here: kiro.dev/blog/specs-bug…

(2/3) That's where Design-first Specs come in 👏 Let's be real, most code isn't greenfield. You're building on top of something that already exists, and you have to work within that architecture whether you like it or not. Design-first lets you start from there, your existing stack, constraints, and system design. Kiro generates the design doc, you iterate, and then it derives requirements from your design. It meets you where your code already is (Or where your favorite Rust crate is 🦀)

(1/3) So you know there's more than one type of Spec in Kiro, right? 👀 The classic Feature Spec starts with requirements > design > tasks. You describe what you want, Kiro figures out how. Great for greenfield stuff where you're starting fresh and your options are wide open. But what if you already know the tech stack? What if you already have chosen your favorite frameworks?

Your IDE shouldn’t cost more than your textbooks.📚 Kiro is free for students at select schools for a full year. Start shipping today — on us. Schools included 🎓 Cal State Fullerton, Waterloo, NYU, Georgia Tech, CMU, ASU, Cal Poly, UChicago, UT Austin, University of Toronto, Hampton University. Share what you’re building with us using #KiroStudents. Get started in the IDE or CLI now 👉 spr.ly/6017B6pd2h

Open weight models in Kiro just got wider reach. 👻 MiniMax M2.1, Qwen3 Coder Next, and DeepSeek V3.2 → now available to IdC users. Plus M2.1 and Qwen3 Coder Next → now live in AWS Europe (Frankfurt) alongside AWS US-East-1. spr.ly/6017B6T8oZ

What are developers saying about Kiro? 🤔 Amarinder Singh went from 7-week prototype cycles to something much faster with structured planning, auto-updating specs, and code that actually matches the original vision. How much time are you losing to unstructured code?

“Which MCP servers are your devs connecting to?” 🤔 That question can kill enterprise AI tool rollouts. Today we give you the answer. Kiro now lets admins allow list approved MCP servers and control which models developers can access, enforced across every IDE and CLI in your org. Get started now 👉 spr.ly/6013B6KjmX

David Yanacek is a Senior Principal Engineer and a lead advisor on the Agentic AI team at @awscloud. He joins @kbal11 to discuss @kirodotdev, Bedrock AgentCore, spec driven development, frontier agents, and the future of agentic software development. @dyanacek bit.ly/4kRGSCg

Just set up Managed Payments (Merchant of Record solution, currently in public preview) from @stripe . I wired it into an existing app using the Stripe Power in @kirodotdev . The Power read my pricing page, created the products/prices in Stripe via MCP, and set up the checkout endpoint. Went from static pricing cards to working subscription with MoR checkout pretty fast.

Ever load a large codebase into your AI and watch it slowly lose the plot? That’s your context window hitting 90%. One agent, too much to hold, confused output. Sub-agents fix this: · Database · Frontend components · Test files Each gets a clean context window. Each runs in parallel. Focused results. Try sub-agents in Kiro and see the difference yourself. 👉 spr.ly/6016htoKK

Most bug reports describe what broke, not what must stay the same. That gap is where AI agents cause regressions. They fix the reported issue and quietly break something adjacent. Kiro works with you to make three things explicit before a single line of code gets written, what's broken, what should happen instead, and what must not change. The fix stays surgical because the boundary is defined upfront. Read how it works 👉 spr.ly/6017hUD7S

Calling all designers and devs 📣 We’re going live today at 9:30 am PT with @figma to show you how the Figma power streamlines your design-to-development workflows. From mapping code components to generating architecture diagrams. Less back-and-forth. More shipping. You won't want to miss it 👉 spr.ly/6016hUO4k

In case you missed it, Specs just got a lot more flexible. Two new Spec types shipped last week. Design-first for when you already have the architecture mapped out and just need help implementing it. Bugfix for when you know what’s broken and need a surgical fix without touching anything else. Download or restart Kiro to try it now 👉 spr.ly/6010hUDjm

Designers and devs, this one’s for you 🎨 We’re going live Wednesday at 9:30 am PT with @Figma to show how the Figma power streamlines your design-to-development workflows From mapping code components to generating architecture diagrams. Less back-and-forth. More shipping. You won't want to miss it 👉spr.ly/6018hm7s2

Agent Skills - How to go from code to shipped product marketing without leaving @kirodotdev for SaaS. Most devs build the thing but never properly market it. The gap between "it works" and "people know it exists" stays open. Here's one way to help close it with @vercel `skills add` + @Remotion video + @coreyhainesco marketing skills

We are excited to welcome Vinicius Senger, Senior Developer Advocate at @kirodotdev, to the DeveloperWeek 2026! Join us to see how humans and AI are collaborating as co-developers to build the next generation of ‘’Renescent Software.’’

Kiro brings agentic power to wherever you build—including the most restricted environments🛡️ Kiro is now available in AWS GovCloud (US) Regions. You get the same agentic AI experience, native MCP support, and private connectivity options designed for highly regulated environments. No compromises on capability, no workarounds for compliance. Learn more here 👉 spr.ly/6015hgDYW

What if your bug fix also defined what must never change and actually validated that? 👀 Kiro just shipped Bug Fix Specs. Instead of patching, Kiro defines: • Current behavior • Expected behavior • Unchanged behavior Kiro generates property based tests across all three. Got a bug you’ve been avoiding? Point Kiro at it now 👉 spr.ly/6012h5oom #Kiro #BuildwithKiro #AICoding

We just shipped Kiro CLI v1.26 👻 Shaped by your feedback, packed with small but important enhancements and fixes that keep making the CLI better and better. What’s new: - Include file contents or directory trees directly in your messages using @path syntax. Tab completion and syntax highlighting makes it easier to reference files quickly - The default agent supports skills out of the box. Just drop them in ~/.kiro/skills - You can now add the code tool for ACPs and subagents Run /changelog command to see the full list of updates made 👉 spr.ly/6015hdv1J

Claude Sonnet 4.6 is live in Kiro. It delivers reasoning closer to Opus and improves token efficiency over Sonnet 4.5. It can: • Build, refactor, and debug with context intact • Maintain long spec workflows • Handle tool calls and subagents Available in the IDE and CLI for Pro, Pro+, and Power users. Restart Kiro and put it to work. 👉 spr.ly/6017hjKiT #Kiro #Kirodotdev #AICoding