AI Services Market › Use cases › Software & DevOps
Software & DevOpsDone with custom-built or unnamed agent Oct 16, 2026
Check code against user intent with review agents and tests
A developer has agents re-read all user messages to re-derive intent, then checks code and tests against it, tracking work in a reviewed todo file.
- What They Did
- The developer has the agent re-read every user message posted in a project to derive a fresh statement of what the user wanted, then uses that to check the code and tests. For long work, the agent writes a todo list kept as a project document, recording feedback on what happened as each gate closes. Tests, logging, and interacting with the running app support this.
- How It Went
- The developer says they have used this approach for about half a year to cut bugs and keep code matching intent. No bug counts or other measurements are given.
- Worth Knowing
- Re-reading all user messages takes only a few minutes even on a project with 10,000 messages, and the task file gets reviewed twice, before and after implementation.
Try it yourself with custom-built or unnamed agent
Read all of my messages in this session and re-derive what I actually wanted, written as a short list of requirements. Then check the code and tests in [folder or branch] against that list and report anything missing, extra, or untested. Record the gaps in a file called todo-review.md and stop there, without editing code until I approve the list.