skills.rest
cpmappstudio
cpmappstudioOFFICIAL
Explore all skills by this author →
GitHub

avoid-feature-creep

Enforce MVP scope guardrails and decision logs during product planning.

Updated Nov 2, 2025
Search Tags:#mvp#backlog#decision-log#feature-creep#scope-management#ai-guidelines#scope-doc
One-click install
npx skills add https://github.com/cpmappstudio/cpca-sports --skill avoid-feature-creep-cpmappstudio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: avoid-feature-creep
Source: https://github.com/cpmappstudio/cpca-sports/tree/main/.agents/skills/avoid-feature-creep
Command: npx skills add https://github.com/cpmappstudio/cpca-sports --skill avoid-feature-creep-cpmappstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents feature creep by enforcing disciplined scoping during product planning.

Core Features & Use Cases

  • Define MVP scope and guardrails to prevent scope expansion.
  • Enforce backlog hygiene and a 48-hour rule before adding new items.
  • Maintain a Scope Decision Log and formal templates for scope decisions.
  • Provide AI-specific guidelines to keep AI-assisted product work focused.

Quick Start

Start by documenting your MVP scope, decision criteria, and guardrails before evaluating new feature requests.

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 during product roadmap planning?▼

Prevent feature creep by applying disciplined scoping mechanisms like MVP scope templates, a Scope Decision Log, and guardrails such as the 48-Hour Rule to evaluate all new feature requests.

What is the 48-Hour Rule for backlog hygiene?▼

The 48-Hour Rule is a backlog hygiene guardrail enforcing a mandatory waiting period before adding new items, ensuring disciplined scope management and preventing impulsive feature additions.

How do I manage MVP scope when reviewing incoming feature requests?▼

Manage MVP scope by maintaining a Scope Decision Log and formal templates to evaluate feature requests against predefined guardrails, ensuring new additions align with documented scope boundaries.

Are there specific AI guidelines for keeping AI-assisted product planning focused?▼

Yes, AI-specific guidelines provide guardrails to keep AI-assisted product planning focused, ensuring AI agents adhere to disciplined scoping rules and MVP scope documents when managing backlogs.

Can I use a scope document to enforce backlog decisions for engineering teams?▼

Yes, an MVP scope document combined with a Scope Decision Log provides formal templates and guardrails to help engineers and product managers maintain backlog hygiene and enforce disciplined scoping.

When should I not use strict MVP scope templates for product management?▼

Strict MVP scope templates may be unnecessary for early-stage exploratory projects lacking a defined backlog, but they are essential for preventing feature creep once roadmap planning and feature requests scale.

Related Skills

Explore More Product & Management Skills→
MrGKanevMrGKanev

avoid-feature-creep

Enforce MVP scope controls during feature planning and backlog reviews.

Community
Basic
elophantoelophanto
116

sprint-prioritization

Generates sprint-ready task lists with optimized schedules and assigned resources from a single project goal.

Community
Intermediate
johannesfritzjohannesfritz
1

prioritization-framework

Score backlog items using RICE, ICE, and MoSCoW frameworks.

Community
Basic
Omar-ObandoOmar-Obando
44

agile-project-management

Standardize Scrum and Kanban workflows with sprint planning, backlog grooming, and velocity tracking.

Community
Intermediate