avoid-feature-creep
Stay focused on core problems, ship faster, and avoid bloated products through disciplined scope management.
- Provides a five-step decision framework (validate problem, check alignment, measure impact, assess complexity, gut check) to evaluate every feature request before building
- Includes scope management rules: define your MVP upfront, track scope changes like code, apply a 48-hour waiting period for new requests, and use budget-based trade-offs to prevent additions
- Offers templates for saying no to stakeholders, executives, users, and AI agents, plus a scope decision log to document all feature choices
- Addresses AI-specific risks: validates that AI features solve real tasks, measures actual usage, and treats agent suggestions as stakeholder requests subject to the same rigor
- Includes recovery strategies for already-bloated products and session discipline checks for AI-assisted development to prevent mid-build scope 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
More from waynesutton/convexskills
convex
Umbrella skill for all Convex development patterns. Routes to specific skills like convex-functions, convex-realtime, convex-agents, etc.
5.5Kconvex-best-practices
Guidelines for building production-ready Convex apps covering function organization, query patterns, validation, TypeScript usage, error handling, and the Zen of Convex design philosophy
3.1Kconvex-functions
Writing queries, mutations, actions, and HTTP actions with proper argument validation, error handling, internal functions, and runtime considerations
2.4Kconvex-schema-validator
Defining and validating database schemas with proper typing, index configuration, optional fields, unions, and migration strategies for schema changes
2.2Kconvex-realtime
Patterns for building reactive apps including subscription management, optimistic updates, cache behavior, and paginated queries with cursor-based loading
2.1Kconvex-cron-jobs
Scheduled function patterns for background tasks including interval scheduling, cron expressions, job monitoring, retry strategies, and best practices for long-running tasks
2.0K