Avoid Feature Creep

# Avoid Feature Creep for Agents

Stop building features nobody needs. This skill helps you ship products that solve real problems without drowning in unnecessary complexity.

Feature creep kills products. It delays launches, burns budgets, exhausts teams, and creates software nobody wants to use. The most successful products do fewer things well.

## The Core Problem

Feature creep is the gradual accumulation of features beyond what your product needs to deliver value. It happens slowly, then all at once.

**Warning signs you're in trouble:**
- Release scope keeps growing without clear user value
- You're copying competitor features without validating need
- Stakeholders keep adding "just one more thing"
- The codebase is getting harder to maintain
- Users complain the product is confusing or bloated
- You haven't shipped in months

**What it costs:**
- Development time on features 80% of users never touch
- Increased bug surface area
- Team burnout and context switching
- Delayed time-to-market
- Technical debt that compounds
- User confusion and abandonment

## Decision Framework

Before adding ANY feature, run through this checklist:

```
1. VALIDATE THE PROBLEM
   Does this solve a real, validated user pain point?
   Have we talked to actual users about this need?
   What evidence supports building this?

2. CHECK ALIGNMENT
   Does this support the core product vision?
   Would this delay our current release?
   What are we NOT building if we build this?

3. MEASURE IMPACT
   How will we know if this feature succeeds?
   What KPIs will change?
   Can we quantify the value (time saved, revenue, retention)?

4. ASSESS COMPLEXITY
   What's the true cost (build + test + maintain + document)?
   Does this add dependencies or technical debt?
   Can we ship a simpler version first?

5. FINAL GUT CHECK
   Would we delay launch by a month for this feature?
   Is this a differentiator or just table stakes?
   Would removing this harm the core experience?
```

If you can't answer YES to questions 1-3 with evidence, do not build the feature.

## Scope Management Rules

**Rule 1: Define and Defend Your MVP**
Write down exactly what "done" means before you start. Document what you're NOT building. Reference this constantly.

**Rule 2: Use Version Control for Scope**
Treat scope like code. Track changes. Require approval for additions.

**Rule 3: The 48-Hour Rule**
When someone requests a new feature, wait 48 hours before adding it to the backlog. Most "urgent" requests feel less urgent after reflection.

**Rule 4: Budget-Based Scoping**
Every feature has a cost. When something new comes in, something else must go out.
"Yes, we can add that. Which of these three features should we cut to make room?"

## Saying No

**To stakeholders:** "That's an interesting idea. Based on our user research, it doesn't solve our core user's top three problems. Let's add it to the v2 consideration list."

**To executives:** "I understand the value. If we add this, we'll delay launch by X weeks and deprioritize Y feature. Here are the trade-offs."

**To yourself:** "Is this scratching my own itch or solving a real user problem? Would I bet the release date on this?"

**To AI agents:** "Stop. Before we add this feature, answer: Does this solve the core user problem we defined at the start? If not, add it to DEFERRED.md and stay focused."

## AI-Specific Guidelines

**AI Feature Creep Red Flags:**
- Adding AI because "everyone else is"
- Building AI summaries without validating users want them
- Multiple AI features without clear differentiation

**Before adding any AI feature, answer:**
- What specific task does this automate?
- How is this better than the non-AI alternative?
- What happens when the AI is wrong?
- Can we ship without this AI feature?

## The Golden Rule

**Ship something small that works. Then iterate based on real usage data.**

Every feature you don't build is: time you get back, bugs you don't fix, docs you don't write, code you don't maintain, confusion you don't add.

The best products aren't the ones with the most features. They're the ones that do the right things exceptionally well.

*"Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away."* — Antoine de Saint-Exupery