KiroEnsemble: an enterprise-grade multi-agent framework that turns Kiro CLI into a full dev team 🚀
Kiro CLI is powerful for single tasks. KiroEnsemble turns it into an entire development team.
If you use Kiro CLI, you know it's great for single tasks at your desk. But I wanted it to carry a whole feature the way a real developer does:
- plan it
- build it
- test it
- review it
- document it
- and open the PR
- without me driving every keystroke.
So I turned it into a team. A lead agent orchestrates and never writes code itself: a builder writes the code, a validator runs the tests and checks the spec, a reviewer diffs the branch, and a documenter writes the docs
You hand it a ticket or a spec, and it delivers a tested, reviewed, documented, PR-ready change. No babysitting.
This isn't a toy. It's enterprise-grade, used by engineers within a renowned international company.
📊 It runs as a full-stack developer on live enterprise codebase:
in one month, straight from personal session logs (using /record-session custom skill):
- 20+ tickets shipped across 4 repos
- 89% completed clean (18 success, 2 partial, 0 failed)
- Features and bug fixes delivered, with tests, documentation and code review on every run
It picks up a ticket, builds it, tests it, reviews its own diff, documents it, and hands back a PR. That's the job of a full-stack dev, and it does it on real, conventions-heavy enterprise repos.
🏗 It also builds projects from scratch:
Point it at an empty directory and it ships. My portfolio site (https://mmo.sidihub.cloud/) and its AI assistant were built end to end by this team, from spec to deployment.
- ⚙️ Why it holds up where other agent setups fall apart
- 🧠 Real separation of roles, not one model pretending to be five.
- 📋 Spec-driven: requirements, design, and tasks, so it builds what you asked for.
- 🪶 Lean orchestrator: the lead never loads your code, so context stays sharp across long runs.
- 🔁 Self-correcting: bounded retries with a diagnostician pass before giving up.
- 🎫 Process-aware: reads tickets, follows your branch and commit conventions, opens the MR, posts the summary.
- ✍️ Grounded knowledge and context through typed files & can be integrated with obsidian
- 🔒 Safe by default: a guard blocks destructive commands and asks before anything risky.
🛠 How it works
Clone the repo, copy the .kiro setup into your desired repo, and either manually edit the conventions and names to fit your needs & project, or ask kiro to adapt it, 5~ minutes setup.
- Prepare a Spec or a Plan document for what you want to work on.
- Start a kiro-cli session -> type `/agent swap team-lead`
- prompt the team-lead to pickup the spec and start the agentic workflow
NOTE: Agents have pre-chosen models that I personally use, edit the agent configs to change the models to your credit budget.
GitHub Repo: https://github.com/Moifek/kiro-ensemble
Free and open-source (MIT). Clone it, run it on your own project, and tell me where it breaks.
Roadmap: Better logging & Mobile integration
What's the most complex thing you'd trust an agent team to ship for you?
Hey u/few_Map7816 I'll be trying to make this work with your solution :D let's connect !
