avoid-feature-creeplisted
Install: claude install-skill waynesutton/builder-skills
# Avoid feature creep
The request sets the scope. Everything the diff contains should trace back to a sentence in the ask. Anything else is a suggestion, not a change.
## The core rule
Build what was asked. Not what would be nice, not what a senior engineer would also do, not what the codebase "should" have. If a line of the diff cannot be justified by the request, it does not belong in the diff.
This applies to product scope and to code scope. A PRD that grows past its problem statement has the same disease as a bug fix that ships with a refactor.
## Signals that creep is starting
Stop when you notice any of these:
- "While we're here" or "might as well" appears in your reasoning
- Adding a config option, flag, or parameter for a case nobody asked about
- Refactoring code adjacent to the change because it looked untidy
- Adding a second feature to make the first one feel complete
- Adding error handling for edge cases the user has never hit
- Adding tests, types, or docs for code outside the change
- Generalizing a one off into a reusable abstraction
- Copying a competitor feature without a stated user need
- A PRD section titled "Future" or "Nice to have" that keeps getting longer
- The change touches a file the request never implied
Each of these might be a good idea. None of them are in scope unless the user says so.
## What to do instead
1. Finish the ask. Ship the smallest change that fully answers the request.
2. Collect the extras as you go. Do not act on th