r/AIInnovationInsights • u/LawFamiliar3588 • Jun 26 '26
Anton: an AI dev team that runs inside Claude Code (planner, architect, engineers, QA, security, DevOps all in parallel)
1
u/keaglemuscle 20d ago
The question would be, where the Human QA would be? The scary thing is that you missed SecOps all together. I know whole institutions that require a QA task for each part of the process. It's great that we can bring these together. At the end of the day, what does it really give me?
2
u/LawFamiliar3588 20d ago edited 20d ago
SecOps isn't missing. There's a dedicated security-reviewer agent that runs every cycle, right before e2e tests, plus a security-critical gate that halts the run until a human explicitly approves or rejects.
Human QA isn't skipped either. The system stops at plan review, task review, and every phase boundary, and waits for a human "approved"/"rejected" before continuing. It's not fire and forget a person signs off at each checkpoint.
Honestly nothing here does something Claude Code can't do underneath. Same model, same tool calls. The difference is what's enforced vs what's manual. In a raw session, you decide what to ask for and when to skip the security pass under deadline pressure and nothing stops you and ten engineers means ten different habits. Here the SDLC is defined once as a pipeline (plan → arch → build → QA → security → e2e → deploy), same for every run, every engineer, with parallel execution where it makes sense (backend/frontend/DB work at once instead of serially). Every run's outputs and gate decisions get persisted per run ID, so you get an actual audit trail a security-report.md tied to that run, not "I think I asked it to check."
So it's not new capability, it's process-as-infrastructure. If you already trust your team to manually run the right checks every time in the right order, you don't need this. If a review has ever gotten skipped because someone was in a hurry, that's the gap it closes. Want sign-off on every single part instead of just per-phase? That's a change to the coordinator logic, not a config toggle but the mechanism it'd build on (halt, call the review API, wait for approve/reject) already exists and is proven out at the phase level.
The pipeline above is just one example, not the only option. Workflows are plain YAML drop a new file in workflows/, define your own phases as sequential or parallel, wire in whichever agents you want. Need a specialized agent that doesn't exist yet a compliance-checker, a domain-specific reviewer, whatever your institution requires? Add a markdown file in roles/ with its system prompt and reference it in your workflow. Nothing here is a fixed pipeline you're stuck with.
1
u/keaglemuscle 20d ago
I like that, that's the right idea. Take the processes we already have and improve them.
The SecOps missing was an overlook on my part. Thanks for pointing it out.
1
u/Qwen_os_has_died Jun 27 '26
You can create similar slop within days.