
ALT Two cycles shown side by side. On the left, "Prompting agents yourself," a human tracks bugs by hand. The loop goes from new work to align, implement, and deploy, then stops at a red question mark labeled "No agent watching the deploy." On the right, "Closing the loop," an "Error monitor watches for bugs" step after deploy sends a green arrow back to "New work assigned," so the cycle restarts on its own.

ALT A flowchart of an agent-driven software factory loop. A new task or issue goes to a triage agent, which routes it four ways: automatable (straight to implementation), needs specs (spec agent, then human spec review, looping back for revisions until approved, then implementation), needs human clarification (human input, then triage again), or park for now. After implementation, agents handle code review and verification. A human then reviews the code and verification output and decides if it's ready to ship. If not, it goes back to code review. If approved, it goes through CI/CD and ships. A monitoring agent then checks for issues: if one is found, a new issue is created and the factory loop starts over; if not, monitoring continues.

ALT A flowchart of an agent-driven software factory loop. A new task or issue goes to a triage agent, which routes it four ways: automatable (straight to implementation), needs specs (spec agent, then human spec review, looping back for revisions until approved, then implementation), needs human clarification (human input, then triage again), or park for now. After implementation, agents handle code review and verification. A human then reviews the code and verification output and decides if it's ready to ship. If not, it goes back to code review. If approved, it goes through CI/CD and ships. A monitoring agent then checks for issues: if one is found, a new issue is created and the factory loop starts over; if not, monitoring continues.















