avoid-feature-creep

To prevent feature creep when building an MVP, use scope management rules and decision frameworks that validate feature requests against core goals before implementation. This ensures focus on essential functionality and faster launches.

Evaluating new feature requests requires checking alignment with core goals, validating if they solve a core user problem, assessing complexity, and determining what existing backlog items must be de-prioritized to build them.

Managing AI coding assistants involves applying AI discipline rules that enforce scope management criteria, preventing AI agents from introducing unnecessary features or complexity outside the defined MVP scope.

Yes, this provides templates for politely but firmly declining out-of-scope requests from stakeholders and users, ensuring that late-stage nice-to-have features do not dilute core product value or delay launches.

You should not add a new feature late in the development cycle if it fails impact measurement and alignment criteria, as adding nice-to-have features without de-prioritizing others causes product bloat and delayed launches.