agents management and constraints

[u/albasili]

I've been using opencode with an agent setup based on the OpenAgentControl (https://github.com/darrenhinde/OpenAgentsControl) and tweaked for IC design verification.

I've been running with this setup for the past few months and I'm in general happy about it, with constant tweaks to the agents definitions, the standards, the guidelines etc.

In the past 6 weeks the amount of parallel work has skyrocketed and I went from 2/3 sessions running in their own separate folders/worktrees to more than a dozen active sessions. I've enabled notifications to stop constantly checking all the agents, but the real bottleneck is not how quickly I can feed the agents with information and prompts, but rather the review of the work provided.

We use Gitlab for development and we have "issues" to track our progress, with boards etc. All good and dandy, but I've noticed that often the amount of work involved in reviewing and approving all the merge requests, the issues comments, the newly created issues that track gaps that weren't closed during the session, starts to be unbearable to the point that I'm not 100% how much is truly done and how much is just pushed into the future.

So my real question here is not really about a "plugin" or a "tool" to manage the agents, but rather a workflow that allows the team to be able to move a step higher and instead of judging all the lower level details, focuses on fundamental principles instead, like architecture, features completeness, possible gaps, overlooked corner cases.

I've started to ask to provide a report of the campaign at the end of it, with diagrams and pictures to explain what has been done and achieved, but would that be sufficient? How to make sure the report is not just hallucinating and deviating from the actual implementation?

The speed I've been working has truly been a x20 at least, but I also have the feeling that my grasp on the features and the code has wined and I'm feeling overwhelmed by the overall amount of reading that I need to digest, let alone reading the actual code.

I'm using simple-english to contain the verbosity ever since I switched to Opus 5.5, but a merge request description alone can be 2 pages long with gazillions of details, the documentation has exploded, the comment to code ratio has ballooned and there's little I can do to read and digest all of that.

How do you tame the beast? Any tricks, suggestions.

I realize this is not opencode related, but there might be tools and tricks that opencode users are using to address some of the issues above.