How do you build the engineering system around AI coding agents for production?
Key_Ad_2747 · reddit · 2026-09-11
A web developer who uses AI coding agents daily argues the hard part is no longer getting agents to write code, but building the system around them. His setup includes per-repo knowledge bases, reusable skills/rules encoding conventions, automated local onboarding, a structured issue → dev → verification → completion workflow, and mandatory pre-completion checks — with the goal of making the agent itself replaceable.
He admits the setup is still cumbersome: onboarding isn't deterministic, context grows too much, rules overlap, and manual intervention remains heavy.
He's also looking for a real control plane above GitHub and coding agents: manage multiple repos, dispatch tasks to different agents in parallel, isolate each task in its own branch/worktree, review progress and PRs, keep GitHub Issues as the source of truth, and stay agent-agnostic. Does something like this exist in practice, or is everyone building their own orchestration layer?
More from coding & agent
- Ten lessons from three years building agents for real production work — garrytan · 2026-09-11
- Devin's New Model Verdict: Not a Benchmaxxer, a 'Killer Execution Model' at $20/Month — brandon_galang · 2026-09-11
- Shopify CEO Tobi Lütke hails single-dev open-source agent harness Pi — aakashgupta · 2026-09-11
- Shopify CEO Tobi Lütke Calls Pi, a Solo-Dev Open-Source Agent Harness, 'the Most Interesting' One — aakashgupta · 2026-09-11
- Dev explains why MCP won him over: organic UX beats telling agents to run CLI commands — zeeg · 2026-09-11
- Sentry Founder: MCP Won Because Agents Can Just 'Fix This URL', Not Call CLIs — zeeg · 2026-09-11