Moscow Prioritization

Categorize features as Must-haves, Should-haves, Could-haves, and Won't-haves.

48 stars 10 forksOther Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill moscow-prioritization
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/product-manager/prioritization/skills/moscow-prioritization ~/.claude/skills/moscow-prioritization

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# MoSCoW Prioritization

Categorize work to manage scope and set clear release boundaries.

## Context

You are planning a release or phase. MoSCoW helps manage expectations and scope creep. Your goal is clear categories that guide engineering and marketing.

## Domain Context

- **Must-haves**: Release cannot ship without these; customer blockers
- **Should-haves**: Important but release is viable without them
- **Could-haves**: Nice-to-have; deprioritized if constraints tighten
- **Won't-haves**: Explicitly out of scope for this release; revisit later

## Instructions

1. **List all features for the release**
2. **Stakeholder alignment**: Get cross-functional input
3. **Categorize each feature**: Must, Should, Could, Won't
4. **Review Must-haves**: Is release truly blocked without them?
5. **Quantify effort**: How much effort for each category?
6. **Plan scope**: If effort is tight, move Shoulds to Coulds/Wonts

## Output Artifact

MoSCoW prioritization list (1-2 pages):
- Features categorized by MoSCoW
- Effort estimate per category
- Release scope and risks
- Post-release backlog (Should/Could moved out)

## Anti-Patterns

- **Everything is a Must**: Scope creep; release becomes impossible
- **Too granular**: Breaking features into too many small items
- **Stakeholder misalignment**: Different departments disagree on categorization
- **Not communicating**: Customers surprised by missing features

## Further Reading

- *Inspired* (Marty Cagan) — scope management
Read the full skill on GitHub

Details

Skill name
moscow-prioritization
Path
product-manager/prioritization/skills/moscow-prioritization/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Moscow Prioritization skill do?

Categorize features as Must-haves, Should-haves, Could-haves, and Won't-haves.

How do I install the Moscow Prioritization skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Moscow Prioritization popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.