avoid-feature-creep

Define MVP scope and review feature requests against user value.

Updated May 4, 2024
One-click install
npx skills add https://github.com/kcrlee/dots --skill avoid-feature-creep-kcrlee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: avoid-feature-creep
Source: https://github.com/kcrlee/dots/tree/main/claude/.claude/skills/avoid-feature-creep
Command: npx skills add https://github.com/kcrlee/dots --skill avoid-feature-creep-kcrlee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams stop scope from expanding beyond what is needed to solve the core user problem, preventing bloated products, delayed launches, and avoidable complexity.

Core Features & Use Cases

  • MVP Scope Control: Define what is in scope, what is out of scope, and what must ship first.
  • Feature Evaluation: Assess new requests against user value, product vision, impact, and complexity before committing.
  • Backlog Discipline: Prune stale ideas, categorize work, and keep the roadmap focused on outcomes.
  • AI Session Guardrails: Keep AI coding assistants aligned with the current objective instead of drifting into extra work.
  • Use Case: A product team preparing a release can use this Skill to reject nonessential additions, document trade-offs, and ship a smaller, clearer first version.

Quick Start

Use this skill to review the current feature list, identify anything that is out of scope, and produce a focused MVP plan with clear trade-offs.

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 in AI product planning?

To prevent feature creep in AI product planning, evaluate new requests against user value and complexity, define strict MVP scope boundaries, and apply decision frameworks to reject nonessential additions before they delay your launch.

What is the best way to prioritize a product backlog for an MVP release?

Prioritizing a product backlog for an MVP release involves pruning stale ideas, categorizing work by outcome, and assessing feature impact versus complexity to keep the roadmap focused strictly on validated user value.

How do I manage scope negotiation with stakeholders during feature review?

Manage scope negotiation with stakeholders during feature review by using structured refusal templates and documenting trade-offs, which helps reject out-of-scope additions while keeping work aligned with the core product vision.

Can I set guardrails to keep AI coding assistants focused on the current objective?

Yes, you can set AI session guardrails to keep AI coding assistants focused on the current objective, preventing the AI from drifting into extra work and expanding scope beyond the defined MVP plan.

Why does my software scope keep expanding beyond the original MVP definition?

Your software scope keeps expanding because of unfiltered feature requests and poor backlog discipline; applying MVP scope control and feature evaluation frameworks stops this bloat by documenting clear trade-offs.