avoid-feature-creep_skill

Overview

This skill prevents feature creep when building software, apps, and AI-powered products. It provides a practical decision framework, scope rules, and communication templates to keep teams focused on the core problem and ship faster. Use it to defend your MVP, manage backlogs, and handle the inevitable "just one more feature" requests.

How this skill works

The skill inspects proposed features against a short checklist: validated user problem, alignment with product vision, measurable impact, and assessed complexity. It offers concrete rules for scope control (MVP definition, 48-hour rule, budget-based scoping) and hands-on guidance for working with AI agents. It also includes recovery steps to audit and remove existing bloat and commands to use during reviews.

When to use it

• During feature planning or sprint grooming to decide what enters the backlog
• When stakeholders or agents request "one more" feature mid-sprint
• While defining an MVP or writing a scope document
• Before adding AI capabilities that may expand scope
• When cleaning up a messy backlog or recovering from bloat

Best practices

• Write and defend a concise MVP scope with explicit out-of-scope items
• Apply the 48-hour rule before committing new requests
• Require a measurable success metric for every feature
• Treat scope like code: track changes and require approvals
• Reserve at least 20% sprint capacity for bug fixes and technical debt

Example use cases

• A PM proposes a new reporting screen during a sprint — use the checklist to defer or swap features
• An AI coding agent suggests multiple enhancements — log the suggestion and apply the 48-hour rule
• Preparing an MVP scope doc before launch, including explicit 'not building' items
• Monthly backlog audit to delete stale entries with no demand or alignment
• Auditing an existing product to find and remove features with <5% engagement