What they did
Michael de Guzman wanted a native text-to-speech wrapper for OutSystems Developer Cloud (ODC) mobile apps, built on the community Capacitor plugin, and wanted to see if Kiro could build it with spec-driven development. He handed Kiro a spec and let it work in spec mode with autopilot and parallel subagents, using the OutSystems MCP to drive Mentor, OutSystems' own asset-building agent. After the first build went wrong he rewrote the spec, switched model per phase (Opus 5.5 for the spec and reviews, Sonnet for the build), and had Kiro write a click-by-click build sheet for the parts he had to do by hand in ODC Studio. He also had Kiro record every lesson in always-loaded steering files.
How it went
The first build reported complete with 39 green tests, but Mentor had made a Reactive library, not a Mobile one, because the reused spec just said library. Kiro had checked completion by counting element names, not wiring, and some work vanished when subagent sessions closed without publishing. The rebuild hit an untested sentence in the spec, which Kiro flagged as a false premise, and Mentor refused to load Mobile assets at all. De Guzman built both assets by hand from the build sheet, correcting several wrong instructions along the way. Both shipped to the Forge and all 7 on-device scenarios passed on a physical iPhone.
Worth knowing
As of mid-October 2026 Mentor through the OutSystems MCP cannot create or load Mobile libraries or Mobile apps, so the agent can only do read-only checks there. Green tests against a mock plugin said nothing about the platform. Unpublished Mentor edits are lost when a session closes, so parallel subagents need a publish step per task.