avoid-feature-creep

Enforce MVP scope and decision frameworks to prevent feature creep.

23|5|Updated Nov 5, 2025

Search Tags:#backlog #decision-framework #product-management #feature-creep #scope-management #mvp-planning #ai-assisted-oversight

Ready to run

npx skills add https://github.com/JStaRFilms/VibeCode-Protocol-Suite --skill avoid-feature-creep-jstarfilms

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: avoid-feature-creep
Source: https://github.com/JStaRFilms/VibeCode-Protocol-Suite/tree/main/assets/.agent/skills/avoid-feature-creep
Command: npx skills add https://github.com/JStaRFilms/VibeCode-Protocol-Suite --skill avoid-feature-creep-jstarfilms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevent feature creep by providing a structured approach to feature scoping, backlog hygiene, and disciplined decision-making in product and AI-assisted development.

Core Features & Use Cases

MVP scope definition: Documents exactly what is in scope and what is out of scope for an MVP.
Decision framework: A step-by-step checklist to validate new features before adding them.
Backlog hygiene: Guidelines to prune the backlog and prevent drift from the core goal.
AI session discipline: Rules for working with AI agents to avoid scope creep and maintain focus. Use case: A product team uses this skill to resist unnecessary feature requests during a sprint planning session.

Quick Start

Outline your MVP scope and apply the decision framework to evaluate any new feature request.

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 during MVP planning?▼

Prevent feature creep during MVP planning by defining exact in-scope and out-of-scope parameters, applying a formal decision framework to evaluate new requests, and enforcing backlog hygiene to maintain core product focus.

What is the best way to manage scope when working with AI assistants?▼

Manage scope with AI assistants by applying AI-session discipline rules that restrict autonomous feature additions, enforce a 48-hour deferral for new ideas, and maintain strict adherence to the defined MVP boundaries.

How do I validate new feature requests before adding them to the product backlog?▼

Validate new feature requests by running them through a step-by-step decision framework checklist that assesses their alignment with MVP scope, preventing drift from the core goal and maintaining strict backlog hygiene.

Can I use a decision framework to groom an existing product backlog?▼

Yes, you can use a decision framework to groom an existing product backlog by applying structured guidelines to prune outdated items, enforce a 48-hour deferral rule for new requests, and prevent scope drift from the core goal.

Why does scope drift happen in product management and how do I stop it?▼

Scope drift happens when unnecessary features bypass formal MVP scope definition and accumulate in the backlog. Stop it by enforcing backlog hygiene, applying a decision framework checklist, and implementing a 48-hour deferral rule.

Does the avoid-feature-creep framework work for sprint planning sessions?▼

Yes, the avoid-feature-creep framework works for sprint planning by providing product teams a structured approach to resist unnecessary feature requests, maintain MVP scope boundaries, and enforce disciplined decision-making.