# How to avoid drifts? — retained record

> Retained reddit record from reddit:ClaudeAI.

Canonical: https://highsignal.app/data/records/e09828ac22c97b37

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:ClaudeAI)  published 2026-10-13 09:39 ingested 2026-10-14 02:37

[original source ↗](https://www.reddit.com/r/ClaudeAI/comments/1x4s8k8/how_to_avoid_drifts/)

## retained text



```
Hello everyone!

What techniques are you using to prevent Claude Code from causing drift in your projects?

To give some context:

I am involved in a PaaS project where we are building a control plane and a new node agent for our platform. I have about a decade of experience architecting and building cloud platforms.

Without getting into too many details, we started by breaking the work down into epics, and within each epic, we have a series of tasks we call "slices." These slices are small portions of work that can be handed over to the AI to execute. Along with them, we provide all the context: general architecture design, overall planning, the specific architectural details being worked on, which components will be created, and details of the expected final result, complete with guard rails to try and prevent deviation.

It started off well, but as the platform took shape, the deviations became larger and larger. I decided to change our workflow to try and reduce these drifts. We shifted our focus to capabilities, further shrinking the size of the deliverables with clear acceptance criteria for what is expected. We still have the same problem, but on a smaller scale.

Because of this, I'd like to know how you have been working with Claude on more complex projects.
```



document fetched 2026-10-14 00:22 · canonical https://reddit.com/r/ClaudeAI/comments/1x4s8k8/how_to_avoid_drifts
