avoid-feature-creeplisted

# 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.