This article is a machine translation of the contents of the following URL, which I wrote in Japanese:
https://qiita.com/Nana_777/items/37a11c9a2f0065158528
Introduction
On July 15, 2025, Japan time, the preview version of Agentic IDE Kiro was released to the public.
It has been a hot topic on social media and technical blogs, so I decided to try it out to see what kind of tool it is.
https://aws.amazon.com/jp/blogs/news/introducing-kiro/
Conclusion
What I did in this article
- I asked the AI to create an API configuration using AWS services, and had it create and implement the requirements, design, and implementation plan.
- I had it implement including the rule files for coding conventions.
- I tried out notable features such as creating an implementation plan from an architecture diagram and displaying differences.
Thoughts
- It's really amazing
- It's super easy to use
- I have free time while waiting (I can do other work)
- I'm impressed that I can create specifications and implementation from an architecture diagram
- I want to go deeper in a later article
Spec-driven development
One of Kiro's distinctive features is SPEC.
Unlike previous Vibe coding, where you communicate with the AI,
you tell the AI the contents of the system you want to build, and the AI organizes the requirements, designs, and makes an implementation plan before starting development.
Spec Tried
As a test, we communicated the following request to configure an AP system to the AI
Please create an API configuration using Amazon API Gateway, AWS Lambda, and Amazon S3 Details are as follows 1. About AWS Lambda ・ Implement the function using TypeScript ・ Make a program that returns a CSV file in Amazon S3 as the result when called from Amazon API Gateway 2. About Amazon S3 ・ Make sure that files in the S3 bucket cannot be accessed directly from the Internet 3. Others - Please make it possible to deploy using CloudFormation templates - Please define CloudFormation templates in YAML format As a result of the request, three documents were generated in order: requirements document (requirements.md), design document (design.md), and implementation plan (tasks.md)
★ Chat replies and deliverables are generated in English at first, but you can have them translated to Japanese midway through.
Requirements document (requirements.md)
The requirements document describes the requirements and acceptance criteria
Design document (design.md)
The design document describes the system configuration diagram, data flow, error cases, test strategy, security considerations, etc.
The configuration diagram is a simple diagram of boxes and letters, but AWS Diagram MCP You should be able to create a separate diagram using AWS service icons by using Server, etc. (This is about how to use the MCP server, not Kiro, so I will omit it here)
Implementation plan (tasks.md)
The implementation plan describes the steps from start to finish of the implementation, such as coding, creating test code, and running tests. If you ask them to implement the following steps, they will execute these steps in order to build the system you requested.
Each step in the implementation plan has a related requirement number, so you can check that none of the requirements have been missed.
Thoughts on creating the document
In a previous article, I introduced AmazonQDeveloper in GitHub. With GitHub, when you communicate your requirements in the same way, they will create the application right away, and you don't know what you'll end up with until the results are out. With Kiro, you can create an implementation plan before you start the implementation, so you can check whether you can achieve what you expected before the implementation, and if there are any deficiencies, you can correct them as you go along with the implementation. I thought it was great that.
https://qiita.com/Nana_777/items/b1339d765c18fc6a0fb4
Experiment: Can we include coding rules checks for implementation content, including our own coding rules, in the process?
With AmazonQDeveloper, we were able to share the rules to be referenced during coding with the AI and have it code. Let's try to see if we can do something similar.
Here, we will prepare coding rules (md files), import them into Kiro, and add a process to check the coding rules based on that.
Coding rules
It seems like you can import the rule file from the button below, but I didn't know how, so I requested it via chat
↓Request text
I would like to include the coding standards that have already been created in the project. I would also like to code the Lambda function according to those coding standards, and add a process to verify that the implementation of the Lambda function has been completed according to the coding standards. The coding convention work has been assigned to the implementation plan
Start implementation plan
To start the implementation plan, click Start task in the implementation plan
When the execution plan starts, Task in The word "progress" and the step currently being worked on are displayed.
At the same time, you can check the work status in more detail in the chat box.
azonaws.com/0/192949/608dd4d6-07c3-4d79-b759-39be82f1688d.png)
When executing any installation commands, you will be asked for permission to execute in the chat field, so please check the contents and execute.
Steering function
I was supposed to upload a file with my own coding rules during TASK1, but the AI didn't ask me to do so,
so I asked the AI how to upload it and was introduced to the Steering function.
It seems that if you upload the rules in the steering folder, it will code according to those rules.
It seems to refer to guidelines and team rules other than coding rules.
When I asked them to create a folder to place rule files, they created various rule files.
If you have your own rules, it's a good idea to rewrite the contents of the created file.
In addition to the coding standards, there was also a file about best practices.
In addition to best practices for each service used in this project, such as Lambda and S3, there were also general security best practices.
For example, if you provide the Well-Architected Framework guidelines, they may configure it in accordance with them.
Continuing the task
There was some chatting in between, but when continuing the task,
the Start of the next task in the implementation plan Click on the task to perform the next task.
Timeline (check the differences)
As the task progresses, the deliverables are updated step by step, but the change history is kept in the form of a timeline, so you can visually check the differences.
Repeat the rest
The work that follows will involve tapping through the tasks.
There are other blogs that introduce the complete process, so please refer to them.
I would like to try more in-depth content, so I will post the results of various experiments separately.
Mysterious button in the chat: Create an implementation plan from an architecture diagram
There is a mysterious button in the chat field, like the icon in the image. If you look at the product page, it says that the implementation is based on the architecture diagram, so I will try it.
I will try it with the configuration diagram introduced in the AWS documentation at the following URL.
Let's pass an image in the chat on the first screen.
Since it couldn't be executed with just the image, let's request the creation of the diagram configuration in text.
As a result, a requirements document, design document, and implementation plan were created, just like in previous verifications.
Thoughts on creating an implementation plan from an architecture diagram
Amazing. If you can create an architecture diagram, you can create the specifications, implementation plan, and even implementation, which is a dream come true.
A revolutionary impression.
Building systems other than AWS
It is also possible to build systems other than AWS.
I tried making a calculator app, and it was fun to see the mock screen and test results displayed in the browser when I ran the test, and to see each execution plan progress visually and clearly.
Top comments (0)