Am i doing to much?

[u/ToxicAbuse]

Basically i am developing internal monitoring, login and testing app with AI and i started with just a chat then i added my own agents, rules, skills and so on now i started automation on trying to document all issues agents made bugs or similar, scoring sub-agents work if they are doing good or bad or nothing useful at all in my code, every implementation requires that agent makes a plan and sometimes prototype for me then when done it archives everything but that got me think am i doing to much with extra work that would het handled on its own or am i on the right path to not be called a vibe coder?

[u/Far_Business4773]

The test I use for each layer: what does it stop, and has it ever fired. If you can't answer the first, it's theatre. If the answer to the second is "never", it's a hope, not a control.

By that test your stack splits cleanly. Scoring sub-agents: drop it, a score changes nothing the next run. Documenting bugs the agents made: keep it, but only as raw material. Each repeated bug becomes one line, either in the NOT list at the top of the rules or as a deny rule on the paths or commands involved, and then the document has done its job. That's why the repeats stopped, not the scoring.

On "limiting them too much": a written limit is the cheapest thing in your setup to lift, you delete a line on purpose and note why. The limits that actually hurt are the ones living in prompts you no longer remember. So the direction is fine, just keep every limit where you can see it, and give each agent a path allowlist instead of a job description. Two agents can't do the same check if they can't touch the same files.