Skip to content
>devspeak
← glossary
patternCommunication Patterns

Implement the smallest scoped change

Ask the agent to change only what's needed to solve this specific problem, touching as few lines and files as possible.

a bit more technical

Limit the fix to the minimum set of changes that resolves the identified cause. Smaller diffs are easier to review, less likely to cause regressions, and simpler to roll back.

picture it

Replacing the one blown bulb instead of rewiring the room. If the light works afterward, you know exactly what fixed it, and nothing else was disturbed.

✗ instead of
fix the button thing on mobile and clean up anything else that looks off while you're in there
✓ try
Fix the misaligned signup button on mobile with the smallest scoped change possible. Only touch what this issue needs. If you notice other problems, list them instead of fixing them.
why it matters

Agents tend to do more than asked: renaming things, adding features, restyling. Every extra change is one more thing that can break and one more thing you must review.

what your agent might say
agent
I kept this to the smallest scoped change: one condition in the date check. I noticed other cleanup opportunities but left them alone. Want a list?
how you might use it
you → your agent
Implement the smallest scoped change that fixes the date bug. Don't touch other files unless it's required, and tell me if you think a bigger change is needed.
common mistake

Thinking smallest means hackiest. The goal is a focused, proper fix. If the right fix is bigger, the agent should say so rather than force a tiny one.

builds on