{"slug": "issue-orchestrator-a-software-engineering-control-plane-for-coding-agents", "title": "Issue-Orchestrator: A Software Engineering Control Plane for Coding Agents", "summary": "A developer built Issue-Orchestrator, a software engineering control plane for coding agents that enforces codebase standards through mechanical checks and state transitions. The open-source project uses GitHub issues and milestones as an external work system, requiring agent output to pass validation before advancing. It aims to make agentic software development resemble traditional software engineering with explicit standards, recoverable state, and human oversight.", "body_md": "Coding agents are very good at finishing bounded tasks.\n\nThey are not, by themselves, good stewards of large systems.\n\nThat distinction is what led me to build Issue-Orchestrator: a software-engineering control plane for coding agents.\n\nThe model is a division of labor.\n\nYou define what \"good\" means for your codebase. Issue-Orchestrator makes those standards enforceable inside the agent workflow.\n\nYou bring the standard:\n\nIssue-Orchestrator brings the enforcement:\n\nThe shift that makes it work is simple: agent output is a claim, not authority.\n\nNothing advances just because an agent says it is done. The orchestrator re-observes GitHub state, worktree state, validation records, and review output before moving an issue forward. Otherwise the work reworks, blocks, or waits for a human.\n\nThis matters because prompt discipline does not scale by itself. You can keep adding instructions telling agents to respect the architecture, write better tests, maintain coverage, and avoid bypassing validation. At some point those instructions become noise. If the standard matters, it needs to be checkable and enforced.\n\nIssue-Orchestrator uses GitHub issues and milestones as the external work system. Large goals become milestones. Milestones become human-sized issues. Issues carry acceptance criteria, labels, dependencies, and enough context for an agent to attempt bounded work without inventing the project plan on the fly.\n\nUnder the dashboard, each running issue is an enforced workflow. The orchestrator delegates to coding, validation, and review steps, but owns the state transitions. The agent can produce work. The system decides whether that work is allowed to advance.\n\nThis is not a fully autonomous coding system, and it is not a prompt collection. It is an attempt to make agentic software development look more like software engineering: explicit standards, mechanical checks, recoverable state, inspectable artifacts, and humans at the merge.\n\nThe project is open source under Apache 2.0:\n\n[https://github.com/BruceBGordon/issue-orchestrator](https://github.com/BruceBGordon/issue-orchestrator)\n\nStatus: early beta. Core orchestration, guardrails, review workflow, and dashboard are in daily use; external setup is still being hardened.\n\nIf you are using coding agents on real repos, I would be interested in how you are handling the same problem: what do you enforce mechanically, what do you leave to review, and where do agents still quietly erode the system?", "url": "https://wpnews.pro/news/issue-orchestrator-a-software-engineering-control-plane-for-coding-agents", "canonical_source": "https://dev.to/brucebgordon/issue-orchestrator-a-software-engineering-control-plane-for-coding-agents-11ii", "published_at": "2026-06-24 15:20:05+00:00", "updated_at": "2026-06-24 15:39:42.033114+00:00", "lang": "en", "topics": ["developer-tools", "ai-agents", "ai-products"], "entities": ["Issue-Orchestrator", "GitHub", "BruceBGordon", "Apache 2.0"], "alternates": {"html": "https://wpnews.pro/news/issue-orchestrator-a-software-engineering-control-plane-for-coding-agents", "markdown": "https://wpnews.pro/news/issue-orchestrator-a-software-engineering-control-plane-for-coding-agents.md", "text": "https://wpnews.pro/news/issue-orchestrator-a-software-engineering-control-plane-for-coding-agents.txt", "jsonld": "https://wpnews.pro/news/issue-orchestrator-a-software-engineering-control-plane-for-coding-agents.jsonld"}}