Changelog

The video shows the Kiro IDE. In the left sidebar under "SPECS", the user clicks "simple-todo-app", which opens a "requirements.md" file titled "Requirements Document" containing an introduction and numbered requirements written as user stories with WHEN/THEN acceptance criteria. A row of tabs reads "1 Requirements", "2 Design", "3 Task list"; the user clicks "2 Design" to reveal a "design.md" file with a layered architecture diagram (User Interface, Application Logic, and Data Layer) and component definitions. The user then clicks "3 Task list" to show a "tasks.md" implementation plan of checkboxed tasks, where the first task is marked "Task completed" and later tasks show "Start task" actions.

The video shows the Kiro IDE. In the left sidebar under "AGENT HOOKS", the user clicks "Code Quality Analyzer", opening its configuration editor for the file ".kiro/hooks/code-quality-analyzer.kiro.hook" with a "Hook enabled" toggle switched on. The panel shows the hook's title and a description ("Monitors source code files for changes and analyzes modified code for potential improvements..."), an "Event" selector with "File Saved" chosen among the options File Created, File Saved, File Deleted, and Manual Trigger, and a "File path(s) to watch" list of glob chips covering JavaScript, TypeScript, JSX, TSX, Python, Java, and C++ files. Below, an "Instructions for Kiro agent" text area lists what to analyze — code smells and anti-patterns, design patterns, language best practices, readability, maintainability, and performance.

The video shows the Kiro IDE. In the left sidebar under "AGENT STEERING", the user clicks through three markdown files. "product.md" opens to a "Product Overview" describing the workspace as a development environment configured for AI-assisted coding with Kiro. "structure.md" shows a "Project Structure" document with a directory tree of the ".kiro/" folder (hooks, specs, and steering subfolders) and file-naming conventions. "tech.md" shows a "Technology Stack" document listing the IDE, platform (macOS), shell (zsh), and common shell commands.

The video shows the Kiro IDE with the "Let's build" chat panel open on the right, using the "Claude Sonnet 4.0" model with "Autopilot" enabled. The user types "Help me get started on the next task" and sends it. Kiro responds by first "Including Steering Documents" — shown as chips for product.md, structure.md, and tech.md — then replies that it sees an existing spec at ".kiro/specs/simple-todo-app" and will check its contents to identify the next task, displaying a "Searched workspace" step while it works.

The video shows the Kiro IDE. In the left sidebar, the "MCP SERVERS" section lists "aws-docs" (Connected), "github" (Connected), and "my-remote-mcp" (Disabled). The user expands "aws-docs" to reveal its tools — read_documentation, search_documentation, and recommend — and opens the "mcp.json" configuration file, which defines each server's command, arguments, and environment (for example, aws-docs runs via "uvx" and github via "npx" with a personal access token). Finally, in the chat input the user invokes a tool by typing "#[aws-docs] read_documentation" and pressing Enter.