AWS Builder Center
What I Learned Building Five Projects in Five Days with Kiro

What I Learned Building Five Projects in Five Days with Kiro

This article shares the projects, technical decisions, challenges, and key takeaways from five days of AI-assisted development, with links to all the open-source repositories.

Sharing, Learning, Growing Together

Five Days of Building with Kiro: My Journey Through the Birthday Daily Coding Challenge

Introduction

When I saw the Kiro Birthday Daily Coding Challenge, I knew it was an opportunity to go beyond experimenting with AI-assisted development. Rather than participating in a single challenge, I committed to completing all five.
Each day introduced a completely different engineering problem from automation with Hooks to custom MCP integrations. The challenge wasn't about building five unrelated demos; it was about exploring how Kiro supports the entire software development lifecycle.
Over five days, I built five open-source projects, each highlighting a different capability of Kiro.

Challenge Overview

DayThemeProject
Day 1Kiro HooksSmart Documentation Sync Hook
Day 2Human + AI CollaborationAI Sprint Room
Day 3AI DebuggingBugFix Task Manager
Day 4Spec-Driven DevelopmentTaskPilot
Day 5Custom MCPNewsPulse MCP
Each project is available on GitHub and demonstrates a practical use case rather than a proof of concept.

Day 1 – Automating Documentation with Kiro Hooks

One of the biggest challenges in software projects is keeping documentation synchronized with source code.
Developers update APIs, rename functions, or change workflows, but documentation is often forgotten until someone reports a problem.
For Day 1, I built Smart Documentation Sync Hook, a Kiro Hook that detects meaningful code changes and automatically updates project documentation.

What it demonstrates

  • Event-driven automation
  • Kiro Hooks
  • Reduced manual documentation work
  • Consistent developer documentation

Day 1 – Automating Documentation with Kiro Hooks

Repository


Day 2 – AI Sprint Room

The second challenge asked builders to create a workspace where humans and AI agents collaborate.
Instead of creating another chatbot, I built AI Sprint Room, a collaborative workspace where users can brainstorm ideas, generate product requirements, produce implementation plans, create sprint tasks, and refine solutions alongside an AI teammate.
The goal was to make AI feel like another engineer participating in the sprint.

Key features

  • Collaborative workspace
  • AI-assisted brainstorming
  • PRD generation
  • Sprint planning
  • Task creation
  • Workflow generation

Day 2 – AI Sprint Room

Repository


Day 3 – Fixing Instead of Building

Software engineering isn't always about creating something new.
Often, the most valuable work is understanding why something is broken.
For this challenge, I worked on BugFix Task Manager, using Kiro Autopilot to investigate failing behavior, identify the root cause, implement the fix, and verify that the application behaved correctly afterward.
Instead of simply patching code, the focus was on preserving existing functionality while resolving the underlying issue.

What I learned

  • Root cause analysis
  • AI-assisted debugging
  • Safe refactoring
  • Regression validation

Day 3 – Fixing Instead of Building

Repository


Day 4 – Building an Application from One Sentence

This was probably the most interesting challenge.
The rules were simple:
Start with one sentence.
Everything else had to come from Kiro Specs.
Using that single prompt, Kiro generated:
  • Requirements
  • Design documentation
  • Implementation tasks
  • Development roadmap
I then followed the generated specification to build TaskPilot, demonstrating how specification-driven development can accelerate the journey from idea to working software.

Key takeaway

Good specifications often matter more than lengthy prompts.

Day 4 – Building an Application from One Sentence

Repository


Day 5 – Extending Kiro with MCP

The final challenge explored one of Kiro's most powerful capabilities Model Context Protocol (MCP).
I built NewsPulse MCP, a custom MCP server that connects Kiro to an external news source, allowing it to retrieve live information and generate responses based on real-time data.
Rather than relying on static knowledge, the integration demonstrated how MCP enables Kiro to interact with external systems securely and meaningfully.

Technologies explored

  • MCP Server
  • External APIs
  • Context-aware AI
  • Real-time information retrieval

Day 5 – Extending Kiro with MCP

Repository


What This Challenge Taught Me

Although each challenge lasted only one day, together they covered a broad range of modern AI-assisted software engineering concepts.
Throughout the week I gained practical experience with:
  • Event-driven automation using Hooks
  • Human-AI collaborative development
  • AI-assisted debugging
  • Spec-driven engineering
  • Custom MCP development
  • AI workflow orchestration
  • Rapid MVP creation
More importantly, I learned that Kiro is much more than an AI coding assistant.
It provides a structured development workflow from planning and specifications to implementation, debugging, automation, and external integrations.

Final Thoughts

The Kiro Birthday Daily Coding Challenge wasn't just about completing five daily tasks it was an opportunity to explore different dimensions of AI-assisted software development.
Each challenge introduced a new mindset:
  • Automate repetitive work.
  • Collaborate with AI instead of simply prompting it.
  • Trust AI to investigate complex bugs.
  • Let specifications guide implementation.
  • Extend AI through external integrations.
By the end of the challenge, I had five open-source projects, a deeper understanding of Kiro's capabilities, and many ideas for future agentic applications.

Happy Birthday, Kiro! 🎉

🏆 Winners will be announced at https://kiro.dev/birthday/2026/winners .
I received 9,000 Kiro Credits for successfully completing all 5 Kiro Birthday Week Coding Challenges consecutively.

Resources link : Kiro: Move beyond AI coding to agentic engineering 

A big thank you to the Kiro team for creating a challenge that encouraged experimentation, learning, and building in public.
I'm excited to continue exploring what's possible with Kiro and the future of AI-powered software engineering.

Thank you for taking the time to read my article! If you found it helpful, feel free to like, share, and drop your thoughts in the comments; I’d love to hear from you.
If you want to connect or dive deeper into cloud, AI and DevOps, feel free to follow me on my socials:
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article