avoid-feature-creep

Apply a 5-step decision framework to prevent feature creep in software projects.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/EricJamesCrow/smartpockets --skill avoid-feature-creep-ericjamescrow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: avoid-feature-creep
Source: https://github.com/EricJamesCrow/smartpockets/tree/main/.claude/skills/avoid-feature-creep
Command: npx skills add https://github.com/EricJamesCrow/smartpockets --skill avoid-feature-creep-ericjamescrow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents teams from adding unnecessary features, helping deliver focused MVPs on time and with less churn.

Core Features & Use Cases

  • Decision Framework: A structured 5-step checklist to validate problems, alignment, impact, complexity, and final gut check before adding features.
  • Scope Management Rules: Templates and processes to define MVP scope, explicitly mark out-of-scope areas, and defend priorities.
  • Backlog Hygiene & AI Session Discipline: Practices to audit backlog items, log scope decisions, and manage AI agent suggestions.
  • Governance & Documentation: Logging decisions, versioning scope changes, and maintaining a single source of truth for scope decisions.

Quick Start

Use the 5-step decision framework and the MVP scope template before accepting 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 product roadmap planning?

Use a structured 5-step decision framework during roadmap planning to validate the core problem, adjust scope, measure impact, assess complexity, and execute a final gut check before approving features.

What is the best way to define MVP scope and mark out-of-scope areas?

Use dedicated scope management templates to define MVP boundaries, explicitly mark out-of-scope areas, and defend priorities to ensure focused releases.

How do I manage AI agent suggestions and backlog hygiene to avoid scope bloat?

Apply backlog governance practices to audit incoming items, log scope decisions, and filter AI agent suggestions through a strict validation checklist to prevent scope bloat.

How do you validate a new feature request before adding it to the backlog?

Run the feature request through a 5-step decision framework to validate problem alignment, evaluate impact versus complexity, and perform a final gut check before backlog insertion.

Does this scope management approach work for logging decisions and versioning changes?

Yes, the approach integrates governance and documentation processes to log decisions, version scope changes, and maintain a single source of truth for product teams.