Engineering video
0:50 · 15 October 2026
The implementer agent acts as the developer that writes the code, utilizing cloud Markdown files for stack guidelines, official provider skills, MCP servers for queries and tools, and sub-agents to work on multiple tickets in parallel.
Hear it at 0:00 →Now, the implementer agent, it's actually the developer and is the one writing the code. So it has access to our cloud MD where we define, okay, whenever you build something, take a look at our design system, or whenever you write an endpoint, use this or check this out, and I kind of define there how we do caching and the database, and pretty much all the stacks so it doesn't have to think too much. Then we have certain skills.
I usually prefer skills from the stack we use, things like Vercel skills for React, AWS skills from AWS. So I want to get as close to the source because I know that the provider usually has the best knowledge on how that technology works, and they package that as a skill. It has access to all our MCP servers, so in in our case, it's Sentry, Posthog, so it can run its own queries, linear, of course, and GitHub.
And there's also different sub agents. So the beautiful thing is you can work in parallel on so many tickets.
