Your coding agent is lying to you about completion. Not maliciously. Not even technically incorrectly, in its own context window, the work does look done. But when a structured verification agent reads the actual files against a detailed specification, the story changes.<\/p>\n\n\n\n
On a recent application build, every time the coding agent reported a phase complete, the verification agent found 30\u201340% of the work was not actually done. Not broken. Not wrong. Simply absent. And the coding agent had no idea.<\/p>\n\n\n\n
This happened across nearly 1,000 verification check items. It took 5\u20136 verification-and-fix iterations to reach 100%. The total human time on the entire engagement, planning through final verification, was 24 hours.<\/p>\n\n\n\n
Here’s what that means for teams running AI coding agents today.<\/p>\n\n\n\n
There’s a specific failure mode that nobody in the AI development tooling conversation is talking about honestly.<\/p>\n\n\n\n
Coding agents are very good at generating code. They’re much less reliable at knowing when they’re done. The agent’s context window has a horizon \u2014 it knows what it built in this session, in this conversation, against the prompt it was given. It doesn’t have a persistent, structured picture of everything the specification required.<\/p>\n\n\n\n
So it reports complete. Confidently, with good reason from its own perspective.<\/p>\n\n\n\n
And 60\u201370% of the spec is implemented.<\/p>\n\n\n\n
This isn’t a corner case. In this build, across multiple verification passes covering nearly 1,000 check items \u2014 data models, API integrations, UI components, payment flows, route guards, real-time subscriptions, test files \u2014 the pattern held consistently. Every “complete” declaration from the coding agent was followed by a verification pass that found roughly a third of the work still missing.<\/p>\n\n\n\n
To be clear: the code that was written was good. The agent built what it said it built. The problem is everything it didn’t mention, the features specified in the plan that simply weren’t there yet.<\/p>\n\n\n\n
This build used a structured verification system with close to 1,000 check items across multiple phases of the project \u2014 organisms, pages, data hooks, API integrations, route guards, payment flows, authentication patterns, test coverage, real-time subscriptions, accessibility.<\/p>\n\n\n\n
Each check item had:<\/p>\n\n\n\n
When the coding agent declared a phase complete, the verification agent ran through the full checklist against the live codebase. It didn’t ask the coding agent what it had built. It read the files.<\/p>\n\n\n\n
The results were consistent across every phase: the coding agent had implemented roughly 30\u201340% of what the specification required. The verification report was handed back. The coding agent fixed the gaps. Another verification pass. More gaps. This cycled 5\u20136 times before a full pass.<\/p>\n\n\n\n
What did those gaps look like in practice?<\/p>\n\n\n\n
A complete registration wizard with four steps \u2014 except Step 4 (payment: Stripe + offline selection) was missing entirely. The UI flowed smoothly to a blank screen.<\/p>\n\n\n\n
Five data hooks written and exported correctly \u2014 but still calling A waitlist feature fully specified in the planning documents \u2014 with status display, position tracking, countdown timer, claim window \u2014 not present at all. Not broken. Just absent.<\/p>\n\n\n\n Route guards protecting dashboard pages \u2014 present on most routes, missing on three. You could navigate directly to admin pages without authentication.<\/p>\n\n\n\n None of these were detectable by looking at the app. They required checking the files against the spec.<\/p>\n\n\n\n For verification to work, you need something to verify against. That’s the other half of this story.<\/p>\n\n\n\n Before a single line of code was written on this build, the project went through five phases of structured AI planning: scope, requirements, architecture, data design, API design, frontend patterns, infrastructure, CI\/CD, testing strategy, and roadmap. Eleven documents, cross-referenced and internally consistent.<\/p>\n\n\n\n Then a structured review pass \u2014 three parallel agents covering scope, architecture, and roadmap simultaneously \u2014 flagged 77 findings. Eleven were critical.<\/p>\n\n\n\n The wrong database technology was documented (PostgreSQL vs DynamoDB). The wrong API paradigm was specified in scope (REST vs GraphQL, contradicting the architecture document). A Step Functions workflow type was chosen that doesn’t support the callback pattern the architecture required. COPPA compliance \u2014 mandatory for a platform serving minors \u2014 was entirely absent from the specification.<\/p>\n\n\n\n These are the findings that, caught during build, cost $15,000\u2013$40,000 each. Caught in planning, they cost an update to a document.<\/p>\n\n\n\n The eleven critical findings and twenty-two major findings were resolved before implementation began. The resulting planning suite became the specification the verification agent ran against across every subsequent phase.<\/p>\n\n\n\n That’s the loop: plans precise enough to verify against, verification rigorous enough to catch what the coding agent missed, iteration fast enough to close the gap before it becomes technical debt.<\/p>\n\n\n\n Let’s look at what this actually cost \u2014 and what it would have cost without it.<\/p>\n\n\n\n Total investment:<\/strong><\/p>\n\n\n\n What the planning phase caught (conservative estimates on avoided downstream cost):<\/strong><\/p>\n\n\n\n What the verification layer caught (conservative estimates on avoided production cost):<\/strong><\/p>\n\n\n\n Conservative avoided cost across planning and verification: $128K\u2013$394K.<\/strong><\/p>\n\n\n\n Return on $3,900 total investment: 33x to 100x.<\/strong><\/p>\n\n\n\n This is the part that usually prompts disbelief: 24 hours of human time for a 5-phase, 11-document planning suite, a full architecture review, and nearly 1,000 check items of implementation verification across multiple sprint phases.<\/p>\n\n\n\n The human wasn’t writing the plans or running the checks. They were directing, reviewing findings, making decisions, and providing the judgment that the agents couldn’t. The agents were doing the systematic work \u2014 generating documents, running parallel review passes, reading codebases, producing verification reports, iterating on fixes.<\/p>\n\n\n\n What a senior engineer’s time bought in this engagement:<\/p>\n\n\n\n That’s 24 hours of high-leverage human judgment, not 24 hours of mechanical checking.<\/p>\n\n\n\n When your coding agent declares a phase complete, how do you know 30\u201340% of the spec isn’t missing?<\/p>\n\n\n\n Most teams don’t have a systematic answer to this question. They have code review \u2014 which catches what was built badly, not what wasn’t built at all. They have QA \u2014 which catches failures in flows that were implemented, not absences of flows that should have been. They have experienced developers who intuitively notice gaps \u2014 but that scales with headcount, not with the number of agents you’re running.<\/p>\n\n\n\n The verification gap is the gap between what the coding agent thinks it built and what the specification required. Closing it needs a system, not a person reading code line by line.<\/p>\n\n\n\n That’s what the planning layer and verification layer together provide: the specification that makes verification possible, and the systematic process that makes it happen at every phase.<\/p>\n\n\n\n The constraint on AI development productivity isn’t the coding agent. It’s the loop around it.<\/p>\n\n\n\nsetTimeout<\/code> with mock data instead of the real AppSync GraphQL client. The app looked functional in every environment. It wasn’t connected to anything.<\/p>\n\n\n\n
\n\n\n\nThe Planning Layer: What You’re Verifying Against<\/h2>\n\n\n\n
\n\n\n\nThe Numbers<\/h2>\n\n\n\n
\n
Planning Finding<\/th> Cost if Found During Build<\/th><\/tr><\/thead> Wrong database technology<\/td> $12K\u2013$18K<\/td><\/tr> Wrong API paradigm<\/td> $20K\u2013$40K<\/td><\/tr> Step Functions constraint violation<\/td> $8K\u2013$15K<\/td><\/tr> COPPA compliance undefined<\/td> $20K\u2013$100K+<\/td><\/tr> SLA contradictions<\/td> $5K\u2013$15K<\/td><\/tr> DR validation absent<\/td> $20K\u2013$50K<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Verification Finding<\/th> Cost if Shipped to Production<\/th><\/tr><\/thead> 5 data hooks returning mock data<\/td> $18K\u2013$36K emergency debugging + rework<\/td><\/tr> Payment flow missing entirely<\/td> $30K\u2013$80K incident + compliance review<\/td><\/tr> Auth guard gaps<\/td> $15K\u2013$30K security incident response<\/td><\/tr> Core features absent (waitlist, registration mutations)<\/td> $20K\u2013$40K sprint + release delay<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
\n\n\n\nThe 24 Hours<\/h2>\n\n\n\n
\n
\n\n\n\nThe Question for Every Team Running Coding Agents<\/h2>\n\n\n\n
\n\n\n\n