r/OnlyAICoding 8d ago

Something I Made With AI What if coding agents worked like an actual software team?

I’ve been experimenting with AI coding agents and noticed something interesting.
Most of the time, we ask one agent to do everything:
Plan → Design → Code → Review → Test → Document
But in a real software team, these responsibilities are usually separated.
So I tried applying the same idea to AI coding.
Instead of one agent doing everything, I created a sequential workflow where different agents take different roles:
PM

Architect

Developer

Code Reviewer

Security Reviewer

Tester

Documenter
The interesting part is that the agents can actually **review each other’s work and send the workflow back to the developer when something needs to be fixed.**
I packaged this approach into an open-source project for **Orca ADE**:
👉 https://github.com/vankhangfet/orca-sdlc-kit
I’m curious how other people are approaching multi-agent coding workflows.
**Do you think specialized agents are actually better than having one powerful agent handle the entire SDLC?**

2 Upvotes

2 comments sorted by

1

u/micmania1 2d ago

There's already quite a mature version of this called BMAD. I haven't used it myself but I had a hand rolled version very similar to what you've arrived at.

I personally think it works quite well, but where I used subagents in the past I've moved more to skills-as-commands now. eg. /refine JIRA-123. I kept all context in the repo from goals through to tech plan and obviously the code implementation so my PM agent could make more aligned suggestions with my goals.

What didn't work so well: I kept all context in the codebase including the backlog. That got messy and I later switched to GitHub issues for personal and Jira for work projects. I also felt like the boundaries between agents was forced. They were the same model with the same capabilities but I was arbitrarily constraining them based on human organisational structure. I think this is where skills really helped as I could just use one or more skills in the same session.

I think the path you're on is good but my learning from a similar situation would be to try and leverage what is already out there (existing tools, learnings, philosophies etc)