---
title: "Comment by Macro8n on \"AI Coding Tip 042 - Stop AI Cowboy Vibe Coding\" | Hashnode"
description: "A practical guardrail for this kind of scope creep: ask the model to name the files and behaviors it intends to change before editing, then compare the final di"
url: "https://hashnode.com/posts/ai-coding-tip-042-stop-ai-cowboy-vibe-coding/6b00be7a599593b7b909e7f8/comment/6b00e8b9e8bff92d9985e1e6"
---

[Discussion](https://hashnode.com/posts/ai-coding-tip-042-stop-ai-cowboy-vibe-coding/6b00be7a599593b7b909e7f8)

Comment [AI Coding Tip 042 - Stop AI Cowboy Vibe Coding](https://hashnode.com/posts/ai-coding-tip-042-stop-ai-cowboy-vibe-coding/6b00be7a599593b7b909e7f8)

[Macro8n](https://hashnode.com/@macro8n)

[1h ago](https://hashnode.com/posts/ai-coding-tip-042-stop-ai-cowboy-vibe-coding/6b00be7a599593b7b909e7f8/comment/6b00e8b9e8bff92d9985e1e6)

A practical guardrail for this kind of scope creep: ask the model to name the files and behaviors it intends to change before editing, then compare the final diff against the requested acceptance criteria. Any extra change needs a reason of its own. A short non-goals list helps too. In your experience, does scope drift show up in the plan or only when you inspect the diff?
