Moscow Prioritization
Categorize features as Must-haves, Should-haves, Could-haves, and Won't-haves.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill moscow-prioritizationgit 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-prioritizationPersonal 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
Details
- Skill name
moscow-prioritization- Repository
- sethdford/claude-skills
- 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
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Multi Region Design
48sethdford/claude-skills
Distribute globally across multiple regions for low latency, compliance, and resilience. Plan data replication, failover, and latency optimization. Use when designing global systems.
Microservices Patterns
48sethdford/claude-skills
Apply proven microservices patterns including saga, circuit breaker, bulkhead, and eventual consistency. Use when designing service-to-service communication and handling distributed failures.
Naming Conventions
48sethdford/claude-skills
Choosing meaningful, pronounceable names that reveal intent for functions, variables, classes, and modules.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.