Avoid Feature Creep

Every developer has worked on a product where "just one more feature" turned into six months of scope creep. This skill gives you the frameworks to actually say no: a five-point decision checklist before adding anything, scope documents you track in git, the 48-hour rule for feature requests, and specific templates for pushing back on stakeholders. It includes guidelines for working with AI coding assistants, which love suggesting improvements that bloat your MVP. The backlog audit section alone will save you from maintaining a graveyard of ideas nobody will ever build. Treat it as a pre-commit hook for your product decisions.

skills.sh installs: 1.2K
GitHub stars: 401
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add waynesutton/convexskills --skill avoid-feature-creep --agent claude-code

Installs into .claude/skills of the current project.

Files

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.