avoid-feature-creep

Feature creep acts as a silent killer for product development, causing bloated codebases, delayed time-to-market, and increased technical debt. This skill provides a structured decision-making framework to evaluate feature requests based on validated user needs rather than impulsive stakeholder additions. It is designed for product managers, software developers, and AI agents acting as technical leads to maintain focus during the entire product lifecycle—from initial MVP scoping to long-term maintenance.

The skill enables users to enforce a disciplined 'ship-first' mentality, ensuring that every requested feature passes a rigorous evaluation checklist. By implementing these practices, teams can avoid the common traps of premature optimization, competitor-chasing, and engineering burnout. It includes specific protocols for managing backlogs, conducting monthly audits to remove inactive features, and communicating trade-offs to stakeholders or project executives effectively.

• Validates requested features against actual user pain points, product vision, and measurable impact (KPIs).

• Provides a standard MVP Scope Document template to define 'in-scope' and 'out-of-scope' boundaries explicitly.

• Implements the 48-hour rule for new feature requests to filter out non-essential additions.

• Offers templates for saying 'no' to stakeholders, executives, and users while maintaining professional relationships.

• Integrates AI-specific guidelines for preventing 'AI-feature-creep' where AI capabilities are added without a clear functional purpose or user benefit.

• Maintains backlog hygiene through routine auditing and pruning of aged, unvalidated, or abandoned backlog items.

• Ideal for software development lifecycle (SDLC) management, sprint planning, and backlog grooming sessions.

• Applicable to any codebase, including those built with frameworks like Convex, React, or Node.js.

• Inputs: User requirements, new feature requests, and existing backlog items. Outputs: Hard-refusal decisions, scoped feature lists, documented trade-offs, and refined product visions.

• Adheres to the principle that development effort must correlate with validated user value to prevent the buildup of technical debt and unnecessary software complexity.