feat/new-feature
Product engineering
New features, specified first
A product brief becomes requirements, design and tasks. Agents build and test each step while you review.
$ kiro --spec-driven
Agree on what to build.
Then let Kiro build it.
Kiro is the agentic IDE and CLI from AWS. Before it writes a line of code, it drafts requirements, a design and a task list that your team can read, question and fix. We help engineering teams roll it out properly: specs, steering, hooks, MCP, and the review habits that make it stick.
by AWS
Explorer
.kiro
specs/refunds
requirements.md
design.md
tasks.md
steering
hooks
src
tests
requirements.mddesign.mdtasks.md
- # Implementation plan
- - [x] 1. Refund model and migration
- _Requirements: 1.1, 1.2_
- - [x] 2. RefundService.create()
- _Requirements: 1.3_
- - [~] 3. Notify payments via SQS
- - [ ] 4. Integration tests
- - [ ] 5. Update API docs
agentworking on task 3 of 5
hookon save: tests/refunds.spec.ts updated ✓
review2 files changed, waiting for you
- 500+ customers worldwide
- 50+ technology alliances
- 24*7 global delivery centre
- 2 offices, India & Dubai
Talk to an engineer
Thinking about Kiro for your team?
Tell us a little about your team and your codebase. One of our engineers will get back to you within one business day. If Kiro is not a good fit for what you are doing, we will tell you.
README.md
What is Kiro?
Most AI coding tools go straight from a prompt to a pile of code. Fine for a demo. Less fine three weeks later, when someone asks why the refund service retries five times and nobody remembers deciding that.
Kiro works the other way round. You describe what you want and it writes a spec first: requirements with acceptance criteria, a technical design, and an ordered list of tasks. You review those, change what is wrong, and only then does the agent work through the tasks, writing code and tests as it goes.
The specs are plain Markdown files in your repo, so the reasoning sits next to the code and goes through review like everything else. Kiro is built on Code OSS, so it feels like VS Code: your settings, themes, keybindings and Open VSX extensions come with you. There is a CLI as well, for people who live in the terminal.
workflow.diff
-prompt > 400 lines of code > "wait, what was this meant to do?"
+prompt > requirements.md > design.md > tasks.md > code you can trace back
- Clarity before codeYou catch the wrong assumption in a requirements doc, not in production.
- Less grunt workAgents take the tasks, tests and docs. Your people keep the hard calls.
- Same rules everywhereSteering files and hooks hold every repo to the same conventions.
- Work others can pick upSpecs are versioned, so a teammate can carry on where you stopped.
.kiro/specs
Spec, design, tasks, code
This is the loop Kiro runs on. Each stage is a file you can open, edit and commit.
-
01 requirements.md
Say what done looks like
Your prompt becomes user stories with acceptance criteria, written in EARS notation. Vague asks turn into statements you can actually test.
WHEN a customer requests a refund within 30 days THE SYSTEM SHALL create a refund record and notify payments
-
02 design.md
Decide the how up front
Kiro reads your codebase and proposes the architecture: components, data models, interfaces and error handling, before anyone starts typing.
## Components - RefundController - RefundService - PaymentsQueue (SQS) ## Errors: retry x3, then DLQ
-
03 tasks.md
Break it into small steps
The design turns into an ordered checklist, each task tied back to a requirement. Run them one at a time and watch what happens.
[x] 1. Refund model + migration [x] 2. RefundService.create() [ ] 3. SQS notification [ ] 4. Integration tests
-
04 src/ + tests/
Agent writes, you review
The agent works the list, writes code and tests, and shows you the diffs. Supervised mode asks before each change. Autopilot just gets on with it.
+ src/refunds/service.ts + tests/refunds.spec.ts ~ docs/refunds.md (hook) ready for review
kiro --help
What you get in the box
Kiro mixes structured planning with agents that do the work. Here is the feature list, minus the marketing.
Ask us how it fits your stackUSAGE kiro [feature] --for your-team
- specs
- Spec-driven developmentPrompt in; requirements, design and a task list out. The agent then works through the list one task at a time.
- hooks
- Agent hooksAutomations that fire when files are saved, created or deleted. Typical jobs: update the tests, refresh the docs, run a security check.
- steering
- Steering filesMarkdown files that tell Kiro how your team builds things: architecture, preferred libraries, naming, and what it should never do.
- mcp
- MCP supportConnect docs, databases, APIs and internal tools through the Model Context Protocol, so the agent works from real context instead of guesses.
- chat
- Agentic chatAsk questions about the codebase, request a change, read the diff, then accept it or throw it away.
- mode
- Autopilot and supervised modesLet the agent run on bigger jobs, or approve every change yourself. Most teams start supervised, which is sensible.
- cli
- Kiro CLIThe same agent in your terminal, for scripting, automation and anyone who would rather not open an IDE.
- editor
- A familiar editorBuilt on Code OSS. Import your VS Code settings and use compatible extensions from Open VSX.
- models
- Frontier modelsRuns on leading models, including Anthropic Claude. That matters most on multi-file changes where the reasoning is the hard part.
engagements/
How we help you adopt Kiro
Buying seats is the easy bit. Getting a team to write good specs and trust the output takes a bit more. Pick the engagement that matches where you are.
# Adoption assessment & pilot
Before anyone buys licences, we look at how your teams actually ship: repos, toolchain, review process. Then we pick one or two real projects and run Kiro on them, measuring before and after so the decision rests on evidence rather than gut feel.
- SDLC and toolchain review
- Pilot team and project selection
- Success metrics such as lead time and defect rate
- Licensing and cost planning
# Enterprise setup, steering & governance
We set Kiro up once, properly, for the whole organisation: shared steering files, an approved list of MCP servers, a library of reusable hooks, and clear rules for secrets and secure coding. New teams start from that baseline instead of a blank folder.
- Organisation-wide steering templates
- Curated MCP server catalogue
- Reusable agent hook library
- Secure coding and secrets policies
# Spec-driven development training
Kiro is only as good as the specs people write and the reviews they do. Our hands-on workshops cover both, for developers, tech leads and product owners, and we build them around your own repos wherever we can.
- Role-based workshops for developers and leads
- Writing and reviewing specs well
- Prompt and steering playbooks
- A champion programme across teams
# Legacy modernisation with Kiro
You know that 3,000-line service nobody wants to touch? Our engineers use Kiro to document it first, put tests around it, and then refactor towards cloud-native patterns on AWS, one reviewed step at a time.
- Codebase discovery and documentation
- Monolith to microservices and serverless refactoring
- Automated test generation
- Migration to AWS managed services
# Amazon Q Developer to Kiro migration
AWS is pointing Amazon Q Developer IDE users towards Kiro. If that is you, we review how your developers use Q today, map plans and subscriptions, move workflows and customisations across, and train people so the switch does not stall a sprint.
- Review of current Q Developer usage
- Plan and subscription mapping
- Workflow and customisation migration
- Change management and training
git branch -a
Where teams put it to work
chore/compliance
BFSI
Code changes that pass audit
Steering files carry your secure coding and audit rules. Hooks run the checks on every change, so nobody has to remember.
refactor/legacy
Legacy modernisation
Making sense of old code
Document legacy applications, then refactor them to modern frameworks with tests wrapped around them first.
infra/iac
Cloud & DevOps
Infrastructure as code
Write and review CloudFormation, CDK and Terraform faster, with the spec recording why the architecture looks the way it does.
test/coverage
Quality engineering
Tests that keep up
Hooks update unit and integration tests whenever code changes, so coverage stops quietly slipping.
main
Startups & ISVs
Prototype to production
Ship the quick version without painting yourself into a corner. The specs are already there when engineer number five joins.
about/consultedge
Why work with us on this
We are an AWS Advanced Tier Partner with our own software engineering practice, and our teams use Kiro on real delivery work. The advice you get on specs, steering and hooks comes from doing it, including finding out what does not work.
- AWS Advanced Tier Partner
- AWS Agentic AI & Generative AI competency badges
- CERT-In empanelled
- ISO 9001:2015 & ISO 27001:2022
- 24*7 global delivery centre
$ consultedge rollout kiro --team yours
- [1/5] assess Review your teams, repositories, toolchain and security requirements.
- [2/5] pilot Run Kiro on real projects and measure before and after.
- [3/5] standardise Build steering, hook and MCP baselines for the organisation.
- [4/5] enable Train developers and leads in spec-driven development.
- [5/5] scale Roll out team by team, with coaching and support while it beds in.
✓ done. Your team owns it from here, and we stay on call.
FAQ.md
Questions we get asked a lot
Something missing? Ask us directly. We would rather answer the real question than the tidy one.
?What is Kiro?
Kiro is an agentic IDE and CLI from AWS built around spec-driven development. You describe what you want, Kiro turns it into requirements, a design and a task list, and then AI agents implement, test and document the work. The aim is to get from prototype to production without losing track of why the code looks the way it does.
?What is spec-driven development?
It means agreeing on what to build before building it. Kiro writes a requirements document with acceptance criteria, a technical design and a list of implementation tasks. Those specs stay in your repository, so every piece of AI-generated code can be traced back to a stated intent.
?What are Kiro agent hooks and steering files?
Agent hooks are automations that run on events such as saving, creating or deleting a file, for example updating tests or documentation. Steering files are Markdown files that tell Kiro about your architecture, conventions and preferred libraries, so its output fits your codebase.
?Can we use our existing VS Code setup?
Yes. Kiro is built on Code OSS, so developers can import their VS Code settings, themes and keybindings and use compatible extensions from the Open VSX registry. The real learning curve is writing and reviewing specs, not the editor.
?How does Kiro relate to Amazon Q Developer?
AWS is positioning Kiro as the next step for AI-assisted development, and Amazon Q Developer users are being guided toward it. We can plan and run that move for you, covering plan mapping, workflow migration and training, so it does not disrupt delivery.
?Is our source code secure with Kiro?
Kiro is built by AWS with enterprise controls, and organisations can manage access through their identity provider. As part of our governance setup we also review data-handling settings, which MCP servers the agent can reach, and how secrets are managed. Tell us your compliance requirements and we will be straight with you about what fits.
?How is Kiro priced?
Kiro has a free tier plus paid individual and team plans based on monthly usage credits. AWS adjusts plans from time to time, so it is worth checking current pricing. We help you pick the right mix for your developers as part of adoption planning.
?Do we need a partner to use Kiro?
No. Any developer can download Kiro and start today. Where we help is the organisation-wide part: governance, shared steering and hooks, training, and a pilot that gives you numbers you can act on.
