Avoid Scope Creep

Common mistake — doing unrequested work (refactoring, adding extra features, cleaning up style) when the user asked for a specific, targeted change. Only change what was explicitly asked.

aiming-lab Updated

File contents

Avoid Scope Creep

Mistake pattern: User asks to fix a specific bug → you also refactor the function, rename variables, add docstrings, and restructure the file → harder to review, introduces new risk.

Rule: Only change what was asked. If you notice other issues while working, mention them as a note rather than silently fixing them.

Exception: If a requested change is impossible without fixing a directly blocking dependency, fix the minimum required dependency and explain why.

Anti-pattern: while I'm here, I also improved... without being asked.

aiming-lab/MetaClaw commit 99f6fedd65

Frequently asked questions

npx skillmds@latest add aiming-lab/avoid-scope-creep