Menu
Recognize scope creep, suggest MVP cuts, and manage project boundaries
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/fabioc-aloha/Alex_Plug_In --skill scope-managementThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
| name | scope-management |
| description | Recognize scope creep, suggest MVP cuts, and manage project boundaries |
| tier | standard |
| applyTo | **/*scope*,**/*mvp*,**/*boundary*,**/*creep* |
Recognize scope creep, suggest MVP cuts, and help maintain healthy project boundaries. The art of delivering the right thing, not everything.
"A good project ships. A perfect project ships never."
Scope management isn't about saying "no" โ it's about saying "yes" to the right things at the right time.
| Signal | Indicator | Response |
|---|---|---|
| Feature addition | "While we're at it, let's also..." | "That's a great idea โ for v2. Let's capture it." |
| Perfectionism | "It's not quite right yet..." | "What's the minimum that solves the problem?" |
| Edge cases | "What if someone does X?" | "How common is X? Let's handle the 80% first." |
| Gold plating | "Users might want..." | "Have users asked for this, or are we guessing?" |
| "This might be useful..." |
| "Let's define done before adding more." |
| Endless research | "We should investigate more..." | "What decision does this research enable?" |
HEALTHY SCOPE:
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ โ
Core Feature โ
โ โ
User Need โ
โ โ
MVP Requirement โ
โ ----------------------------------- โ
โ ๐ Phase 2 (captured, not now) โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
SCOPE CREEP:
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ โ
Core Feature โ
โ โ ๏ธ "Nice to have" โ
โ โ ๏ธ Edge case handling โ
โ โ ๏ธ Extra polish โ
โ โ ๏ธ "While we're here..." โ
โ โ Gold plating โ
โ โ Premature optimization โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
| Priority | Meaning | Criteria |
|---|---|---|
| Must have | Critical path | Won't work without it |
| Should have | Important | Significant value, but workaround exists |
| Could have | Nice to have | Adds polish, not essential |
| Won't have | Out of scope | Explicitly excluded (for now) |
## MVP Definition: [Feature/Project]
### Must Have (Ship-blocking)
- [ ] [Core functionality 1]
- [ ] [Core functionality 2]
### Should Have (Target for v1.0)
- [ ] [Important enhancement 1]
- [ ] [Important enhancement 2]
### Could Have (If time permits)
- [ ] [Nice to have 1]
- [ ] [Nice to have 2]
### Won't Have (Explicitly v2+)
- [ ] [Future idea 1]
- [ ] [Future idea 2]
### Definition of Done
[ ] [Specific, measurable completion criteria]
When someone suggests additions:
"That's a great idea. Let me add it to the backlog for Phase 2
so we don't lose it. For now, let's ship the core first."
When scope must grow:
"We can add X, but something needs to come out to keep the timeline.
Options:
A) Add X, defer Y to next release
B) Add X, extend timeline by Z days
C) Keep current scope, add X to backlog
Which works best for stakeholders?"
When features keep adding:
"Quick check: If we shipped today with just what we have,
would users get value? If yes, maybe we're already at MVP."
When perfectionism strikes:
"This handles the 80% case. The remaining 20% is complex.
Ship now, gather feedback, then decide if the 20% is worth it?"
For good ideas at bad times:
"Great idea but out of scope for this sprint.
Added to the parking lot โ we'll prioritize it next planning."
| Metric | Healthy | Warning | Critical |
|---|---|---|---|
| Requirements | Stable | 1-2 changes/week | Daily changes |
| Timeline | On track | Slipping | Blown |
| Team confidence | High | Uncertain | Low |
| Stakeholder alignment | Clear | Some confusion | Conflicting |
| Done definition | Specific | Vague | Missing |
Calculate scope complexity:
Base features: ___ ร 1 point = ___
Integrations: ___ ร 2 points = ___
Edge cases: ___ ร 1 point = ___
New technologies: ___ ร 3 points = ___
Dependencies: ___ ร 2 points = ___
โโโโโโโโโโโโโโโโโโโโโ
TOTAL: ___
0-10: Simple โ ship fast
11-25: Moderate โ careful planning
26+: Complex โ consider splitting
| Question | If Yes โ |
|---|---|
| "Does this block launch?" | Keep it |
| "Can users workaround this?" | Defer it |
| "Is this proven valuable?" | Keep if proven |
| "Are we guessing about need?" | Validate first |
| "Can this be added later?" | Defer it |
| "Will this delay other must-haves?" | Defer it |
/scopecheck
Output:
๐ Scope Health Report
Current scope: 12 features
- Must have: 5 โ
- Should have: 4 ๐
- Could have: 3 โณ
Complexity score: 18 (Moderate)
Recommendation: Consider deferring 2 "could have" items
to hit timeline with confidence.
Alert when:
Ship small, ship often, ship something.
Based on SOC occupation classification
Create and maintain ASCII visual dashboards for project tracking with parallel lane progress bars
Store and manage voice samples for TTS cloning โ portable, version-controlled audio references
Clear documentation through visual excellence