MoSCoW Prioritization

VerifiedSafe

Categorize items into Must have, Should have, Could have, and Won't have for clear scope and priorities.

Sby Skills Guide Bot
ProductivityBeginner
7/28/2026
Claude CodeCursorWindsurfCopilotCodex
#prioritization#moscow#scope-definition#product-management#planning

Recommended for

Automated summary

This skill applies the MoSCoW method to sort a list of items into Must have, Should have, Could have, and Won't have, with rationale and an effort-distribution estimate.

Strengths

  • Produces a structured, reusable output (per-category checklists, effort distribution table, Red Flags section)
  • Enforces discipline on "Musts" with the test "if we shipped without this, would we fail?"
  • Makes Won't have items explicit, which curbs later scope creep
  • Includes a Rationale section and a concrete next step, so the output leads to action

Limitations

  • Does not produce per-item numeric effort estimates; the percentages in the table are indicative only
  • Quality depends entirely on how complete and well-defined the input list is
  • As the skill itself notes, stakeholder alignment is still required — the output is not a final decision
When to use it

Use it when you need to settle project scope or a feature list and everything feels equally important.

When not to use it

Avoid it if you need a quantified ranking (RICE, scored impact/effort) or if stakeholders are unavailable to validate the trade-offs.

Security analysis

Safe
Quality score88/100

This SKILL.md is a pure text-only instruction template for the MoSCoW prioritization framework. It declares no allowed-tools, contains no shell commands, network calls, file writes, credential handling, or obfuscated payloads. The only dynamic element is a trailing $ARGUMENTS placeholder used to inject the user's item list into the prompt, which carries no execution risk beyond normal prompt input.

No concerns found

How this analysis is made

Examples

Feature list triage
Sort these v2 features into MoSCoW: dark mode, SSO login, CSV export, Slack integration, custom dashboards, mobile app. We have 3 engineers for 8 weeks.
MVP scoping
Use MoSCoW to define the MVP scope for a marketplace app: user accounts, listings, search, payments, reviews, admin panel. Flag anything that isn't truly a Must.
Everything is urgent
My roadmap has 15 items and everything feels equally important. Apply MoSCoW prioritization and tell me what should explicitly go into Won't have this quarter.

name: moscow description: MoSCoW prioritization categorizing items as Must have, Should have, Could have, or Won't have. Use for scope definition, feature prioritization, or when everything feels equally important. user-invocable: true

MoSCoW Prioritization

Categorize items into Must have, Should have, Could have, and Won't have for clear scope and priorities.

Instructions

Take the list of items provided and sort them into MoSCoW categories. Be rigorous about what's truly a "Must"—if the project/goal can still succeed without it, it's not a Must.

Output Format

Context What are we prioritizing for? What are the constraints (time, budget, capacity)?

Prioritized List

Must Have (Critical)

Without these, the project fails or is pointless

  • [ ] [Item] — [Why it's a must]
  • [ ] [Item] — [Why it's a must]

Should Have (Important)

Significantly adds value; painful to omit but project survives

  • [ ] [Item] — [Value it adds]
  • [ ] [Item] — [Value it adds]

Could Have (Nice to Have)

Desirable if time permits; low impact if cut

  • [ ] [Item] — [Why it's optional]
  • [ ] [Item] — [Why it's optional]

Won't Have (Not This Time)

Explicitly out of scope; may revisit later

  • [ ] [Item] — [Why it's deferred]
  • [ ] [Item] — [Why it's deferred]

Effort Distribution

| Category | Items | Est. Effort % | |----------|-------|---------------| | Must | X | ≤60% | | Should | X | ~20% | | Could | X | ~10% | | Won't | X | 0% (deferred) |

Red Flags

  • If Must > 60% of effort: scope may be too large
  • If no Won'ts: probably not being honest about constraints
  • If everything is Must: priorities haven't been set

Rationale Explain the key trade-offs made and the reasoning behind contentious categorizations.

Next Step What's the first Must item to tackle?

Guidelines

  • Ask "If we shipped without this, would we fail?" for each Must
  • Challenge "Musts" that are really "someone really wants this"
  • Make Won'ts explicit—avoids scope creep later
  • Consider dependencies (a Must might require a "hidden" Must)
  • Stakeholder alignment is essential—this isn't just your opinion

$ARGUMENTS

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/moscow-prioritization-ms47vp5l/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/moscow-prioritization-ms47vp5l' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/moscow-prioritization-ms47vp5l/download' --output '.skill-downloads/moscow-prioritization-ms47vp5l/SKILL.md.part' && mv '.skill-downloads/moscow-prioritization-ms47vp5l/SKILL.md.part' '.skill-downloads/moscow-prioritization-ms47vp5l/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/moscow-prioritization-ms47vp5l/SKILL.md' && test -s '.skill-downloads/moscow-prioritization-ms47vp5l/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/moscow' && cp -R '.skill-downloads/moscow-prioritization-ms47vp5l' '.claude/skills/moscow'

Cursor
test -f '.skill-downloads/moscow-prioritization-ms47vp5l/SKILL.md' && test -s '.skill-downloads/moscow-prioritization-ms47vp5l/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/moscow' && cp -R '.skill-downloads/moscow-prioritization-ms47vp5l' '.cursor/skills/moscow'

Codex
test -f '.skill-downloads/moscow-prioritization-ms47vp5l/SKILL.md' && test -s '.skill-downloads/moscow-prioritization-ms47vp5l/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/moscow' && cp -R '.skill-downloads/moscow-prioritization-ms47vp5l' '.agents/skills/moscow'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/moscow-prioritization-ms47vp5l'

openskills read 'moscow-prioritization-ms47vp5l'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/moscow-prioritization-ms47vp5l/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills