Agents say "done" when code is missing. Here's our fix
Summary
The article introduces a CLI tool called 'malveon check' that verifies code completion by running build, lint, and test commands to prevent AI agents from falsely declaring tasks done.
Similar Articles
[Discussion] Do AI coding agents say “done” too early for you too?
Discussion about AI coding agents claiming completion prematurely, skipping checks, and making messy changes. The author is testing a system with planning and review gates to improve AI-coding workflows.
Your coding agent says "done." It never actually checked if the thing works in a browser.
A critique of AI coding agents that claim tasks are complete without verifying functionality in a real browser environment.
The worst coding agent failure is when it says “done” too early
The article highlights a common failure mode in coding agents where they report tasks as 'done' while leaving hidden issues like insufficient tests, missed edge cases, and introduced bugs, creating a trust problem for developers.
Giving an AI coding agent a deterministic "architecture linter" so it stops faking "done"
The article describes giving an AI coding agent a deterministic architecture linter that checks Event Storming diagrams for mechanical gaps and open questions, ensuring the agent doesn't fake completion.
@addyosmani: Verification is one of the most important things for getting great results out of your agent. Clearly define "done" bef…
Addy Osmani emphasizes that verification is crucial for getting good results from AI coding agents: clearly define "done" before review, give the agent executable checks (bash commands, tests, browser tests) to pass, and only ship when nothing blocks merge.