Skip to content
Back to skills

Feature Prioritization Matrix

ASecurity

Transform overwhelming client feature wish lists into structured MVP/Phase 2/Phase 3 plans with time estimates, preventing scope creep and creating profitable upsell opportunities.

  • 666 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added February 8, 2026
tools

Works with

  • cli

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill feature-prioritization-matrix --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Feature Prioritization Matrix?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Feature Prioritization Matrix
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-feature-prioritization-matrix/badge)](https://www.skillsdirectory.com/skills/majiayu000-feature-prioritization-matrix)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: feature-prioritization-matrix
description: Transform overwhelming client feature wish lists into structured MVP/Phase 2/Phase 3 plans with time estimates, preventing scope creep and creating profitable upsell opportunities.
---

# Feature Prioritization Matrix

Turn feature chaos into structured, profitable delivery phases.

## What This Skill Does

You list all features a client wants, and this skill outputs:

✅ **MVP Features** - Must-have for launch (what to build first)
✅ **Phase 2 Features** - Enhanced functionality (post-launch additions)
✅ **Phase 3+ Features** - Nice-to-haves (future roadmap)
✅ **Estimated Build Time** - Realistic hours per phase
✅ **Pricing Structure** - How to charge for phased delivery
✅ **Priority Reasoning** - Why each feature belongs in its phase

## Who This Is For

**Software Tailors** need to prevent scope creep, keep projects manageable, create upsell opportunities, set realistic expectations, and deliver value quickly.

## Prioritization Framework

### MVP (Phase 1) - Must-Have
- Solves core problem
- Blocking other features
- Can't launch without it
- Simple to build

### Phase 2 - Should-Have
- Significantly improves UX
- Automates manual processes
- Clear ROI
- Client proven they use MVP

### Phase 3 - Nice-to-Have
- Competitive differentiator
- Efficiency optimization
- Not urgent

### Future - Maybe Someday
- Expensive to build
- Adds recurring costs
- Unclear ROI

## Presenting Phased Delivery

"I organized features into phases so you see working software in 6 weeks, not 6 months. Phase 1 ($18K) solves your core problem. Phase 2 ($7K) adds automation after you've proven you love it. Phase 3 ($10K) gives you competitive edge. You only commit to $18K today - if Phase 1 doesn't work, you stop. If it's amazing, you invest more."

## Preventing Scope Creep

When client says "Can we just add...?":

"Great idea! [Feature X] takes [Y] hours. Three options:
1. Add to Phase 2 for $[Z]
2. Swap for something in MVP
3. Expand MVP: add $[Z] and push timeline [W] weeks

Which makes sense?"

**Never "just add" features for free.**

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.