メニュー
Recognize scope creep, suggest MVP cuts, and manage project boundaries
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/fabioc-aloha/Alex_Plug_In --skill scope-managementコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
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
SOC 職業分類に基づく
| 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.