[subarctic]

Claude code makes it so easy to do things the "right way" that it also makes it really easy for you to let scope creep get out of hand. I have a personal project that I haven't deployed yet that in some ways is way overengineered for its purpose. It's hard to blame the tool though, it's always telling me I'm making it more complicated than it needs to be but I don't listen

[shepherdjerred]

I've felt this recently. I've often been bad about scope creep. CC makes it so easy.

On the other hand, I can see these tools getting good enough that scope creep doesn't even matter.

ATM I usually get stuck around the review/verification stage. As in, my code works, I have tested that it works, but it is failing CI or someone left a PR comment. And for each comment I'll have to make sure it makes sense, make the change, test again, and get CI passing again.

[lopis]

In my team we have strict rules for scope creep in pull request. Each one needs to introduce a single thing, not a dozen little refactorings. This helps, but not when you're working alone in a personal project. Maybe you can setup your review agent to help with scope creep?