avoid-feature-creep

Evaluate feature requests against MVP scope and decision checklists.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/debsouryadatta/memo-hack --skill avoid-feature-creep-debsouryadatta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: avoid-feature-creep
Source: https://github.com/debsouryadatta/memo-hack/tree/main/.agent/skills/avoid-feature-creep
Command: npx skills add https://github.com/debsouryadatta/memo-hack --skill avoid-feature-creep-debsouryadatta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the uncontrolled addition of features (feature creep) that can delay product launches, increase complexity, and dilute the core value proposition of software and AI products.

Core Features & Use Cases

  • Scope Management: Provides frameworks and rules for defining, defending, and managing product scope.
  • Decision Making: Offers a decision checklist to rigorously evaluate new feature requests against user needs and product vision.
  • Saying No: Provides templates for politely but firmly declining out-of-scope requests from stakeholders, users, and AI agents.
  • AI Discipline: Offers specific guidelines for managing AI-driven suggestions to prevent scope expansion.
  • Use Case: A product manager is about to approve a "quick" feature addition that would delay an MVP launch by two weeks. They use this Skill's decision framework to confirm it doesn't solve a core user problem and defer it to a later version.

Quick Start

Use the avoid-feature-creep skill to evaluate a new feature request by asking: "What user problem does this solve?"

Frequently Asked Questions about avoid-feature-creep

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent feature creep from delaying my MVP launch?

Prevent feature creep by enforcing strict scope management frameworks and using decision checklists to evaluate if new MVP features solve core user problems before approval.

What is the best way to manage scope expansion requests from stakeholders?

Manage scope expansion by using predefined communication templates to politely decline out-of-scope stakeholder requests, ensuring focus remains on the core product value.

How do I evaluate a new feature request against my product vision?

Evaluate a feature request by applying a decision checklist that rigorously validates the proposed addition against current user needs and the overarching product development vision.

How to manage AI-driven suggestions that cause scope expansion in product development?

Manage AI-driven scope expansion by applying specific AI discipline guidelines that evaluate autonomous agent suggestions against defined MVP boundaries to maintain core product focus.

When should I say no to new features during agile product development?

Say no to new features during agile development when a request fails the decision checklist, proving it does not address a core user problem or dilutes current scope.