avoid-feature-creep

Enforces scope discipline and feature validation during software planning and AI coding sessions.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/kausthubh-coder/kriyan-web --skill avoid-feature-creep-kausthubh-coder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: avoid-feature-creep
Source: https://github.com/kausthubh-coder/kriyan-web/tree/main/.cursor/skills/avoid-feature-creep
Command: npx skills add https://github.com/kausthubh-coder/kriyan-web --skill avoid-feature-creep-kausthubh-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature creep delays launches, bloats codebases, and burns teams out by accumulating features nobody validated. This Skill gives developers and AI agents a structured decision framework to reject unnecessary features, defend MVP scope, and ship focused products faster. ## Core Features & Use Cases - Feature Decision Framework: A five-step checklist covering problem validation, alignment, impact measurement, complexity assessment, and a final gut check before any feature is approved. - Scope Management Tools: Templates for MVP scope documents, scope decision logs, MoSCoW prioritization, and the 48-hour rule for incoming requests. - AI Session Discipline: Specific guardrails for working with AI coding agents, including session start/mid/end checks and treating agent suggestions as stakeholder requests. - Use Case: While building an MVP with an AI assistant, the agent suggests adding caching, refactors, and extra error handling. Use this Skill to evaluate each suggestion against the defined scope, log deferred items, and stay focused on shipping the core feature. ## Quick Start Ask the AI to review your current feature list against the MVP scope and flag anything that should be deferred or cut.

Frequently Asked Questions about avoid-feature-creep

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent feature creep in my software project?▼

Define an explicit MVP scope document listing what is in and out of scope, then run every new request through a validation checklist covering user evidence, alignment, and measurable impact. Defer anything that fails validation to a later version.

How to manage scope when coding with AI assistants?▼

State your scope constraints at the start of every AI session and treat agent suggestions like stakeholder requests. Log suggestions in a scope decision log, apply the 48-hour rule, and run mid-session checks asking whether scope has expanded.

What is the MoSCoW prioritization method?▼

MoSCoW categorizes backlog items as Must Have, Should Have, Could Have, or Won't Have. Must Haves are required for the product to function, while Won't Haves are explicitly out of scope, forcing honest prioritization decisions.

When should I say no to a feature request?▼

Say no when the request lacks validated user evidence, does not support the core product vision, or would delay the current release without proportional value. Offer to log it for a future version instead of rejecting it outright.

How do I fix a product that already has too many features?▼

Audit every feature against usage data, categorize them as core, supporting, peripheral, or bloat, then deprecate low-engagement features with a warning period. Add feature flags and usage metrics requirements to prevent recurrence.