Five Agents, Five Documents: How We Build Payment Software with AI at DOKU
The AI-assisted development pipeline I walked through at Kelas Beta: one agent per role, every output a document in git, and a human gate between each step.
Solutions Architect · AI Engineering · Notes
Hi, I'm Firman Hanafi. I work as a Solutions Architect at DOKU — translating product needs into systems that engineers can actually build. This is where I write about architecture patterns, AI for software engineering, and lessons from real projects.
The AI-assisted development pipeline I walked through at Kelas Beta: one agent per role, every output a document in git, and a human gate between each step.
MCP explained for engineers who already know REST, what DOKU exposes to agents through it, and why the tools that aren't on the list matter more than the ones that are.
The n8n agent I built for Kelas Beta: a keripik shop cashier on DOKU's MCP server, and why its real guardrails live in Postgres instead of the system prompt.
Five decision dimensions for choosing AI coding tools, an honest take on the four I've used, and a deliberately short list of the ones I'm watching but haven't tried.