# AI Coding Tip 024 - Force a Criteria Check Before the Task Ends

DevFeed: [AI Coding Tip 024 - Force a Criteria Check Before the Task Ends](<https://devfeed.tech/articles/ai-coding-tip-024-force-a-criteria-check-before-the-task-ends-18214.md>)

Original publisher: [Read original article](<https://maximilianocontieri.com/ai-coding-tip-024-force-a-criteria-check-before-the-task-ends>)

Author: Maxi Contieri

Published: 2026-06-12T23:28:07Z

Content type: tutorial

Language: en

Sources: [Maximiliano Contieri - Software Design](<https://devfeed.tech/sources/maximiliano-contieri-software-design.md>)

Topics: [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [ai-coding](<https://devfeed.tech/topics/ai-coding.md>), [coding](<https://devfeed.tech/topics/coding.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [trust](<https://devfeed.tech/tags/trust.md>), [verification](<https://devfeed.tech/tags/verification.md>)

## AI overview

The article recommends spawning a fresh, read-only subagent after each coding task to verify mandatory rules independently. It proposes checking modified files line by line, requiring explicit PASS or FAIL evidence, and blocking completion until violations are fixed.

## Source excerpt

TL;DR: Spawn a fresh subagent after every task to check your rules, because the AI that did the work can't audit itself. Common Mistake ❌ You write a detailed AGENTS.md with strict mandatory rules. T