Something something we made this, something something sidecar. Just kidding. This isn't a new idea, but it's one that showed good success for me so I am curious if there's a mature platform out there for it. The idea is simple; the LLM makes claims/facts, and then it begins to implement something based on those things it discovered. I've found that many of the claims it made that are wrong can be found correctly if I prompt it to analyze that specific claim in a sub agent. The problem with this technique is it takes a much longer time to complete something because you have to test every claim. The fix for that is to just use a lower reasoning effort on the sub agents. For my model, GLM 5.3 Flash, this works well. I tried no reasoning and it did not hold up very well for coding. For other models the reasoning efforts probably need to be tweaked. Prompting for this technique itself isn't hard, but I think building a harness around it or a plugin for it (Opencode) might be useful so it becomes deterministic. I've been testing this with Rust coding with the Bevy game engine, just for fun. it consistently finds a few claims that are incorrect which is very nice. I basically use the same test, find the highest CPU utilization in the client code and propose optimizations. I use a seed value so that I can iterate over the plugin with Claude. Then I rollback the Opencode v2 session and retry again after making changes to the plugin. The main agent gets back this report which allows it to correct its plan and then start with a much better implementation. https://preview.redd.it/yhdcq7bk9xwh1.png?width=1739&format=png&auto=webp&s=e16a7d8c44e549896518ba47a710e5559cdb9b69 I don't need to spam you with a plugin Claude made from the spec below, but I do recommend trying to make it with or assisted by an LLM. Here are the instructions for OpenCode v2 plugin that is working well for me. I just wrote this (prompt?) by hand and iterated on it a few times. Model: GLM 5.3 Flash Analyze the issue presented (e.g. find highest cpu utilization in this client code) at max reasoning (Agent 1) Generate a report on the components involved and a plan for resolving with references as a .md doc (Agent 1) Submit a link to the .md document to a sub agent at high reasoning to extract all claims along with any relevant context (Agent 2) Submit every claim as a separate sub agent with relevant context at low reasoning, the sub agent should validate only this single claim. Timeout of 5 min per agent. Allow all commands that don't compile software and don't modify source code. (Agent X) All sub agents (Agent X) return results to Agent 2. Agent 2 returns combined report to Agent 1 (return link to .md document not full doc due to tool result size limits). Agent 1 revises plan. Agent 1 asks for confirmation to continue the work/implementation based on the revised plan. This type of workflow, for the lack of a better term, is definitely something we need a library of. Something to bridge the gap between skills and a more structured approach to an issue. Ideally keeping it as deterministic as possible so that the LLM doesn't steer away from the steps.   submitted by   /u/fragment_me [link]   [comments]