skills.rest
wildwasser
wildwasserCOMMUNITY
Explore all skills by this author →
GitHub

moscow

Classify backlog items into Must, Should, Could, and Won't categories.

35|13|Updated Dec 12, 2025
Search Tags:#planning#requirements#prioritization#backlog#stakeholders#feature-prioritization#moscow
One-click install
npx skills add https://github.com/wildwasser/opencode-agents --skill moscow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: moscow
Source: https://github.com/wildwasser/opencode-agents/tree/main/.opencode/skills/moscow
Command: npx skills add https://github.com/wildwasser/opencode-agents --skill moscow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

MoSCoW prioritization helps teams define scope and align on what truly matters by categorizing items as Must have, Should have, Could have, and Won't have.

Core Features & Use Cases

  • Classify backlog items into the four MoSCoW categories to drive scope decisions and sprint planning.
  • Use for feature prioritization, project scoping, or when all items feel equally important to establish clear trade-offs.
  • Real-world example: given a product backlog, determine the Must features for v1 and mark less critical items as Should/Could/Won't.

Quick Start

Sort your project items into Must, Should, Could, and Won't using the MoSCoW method for the current sprint.

Frequently Asked Questions about moscow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize backlog items when everything feels equally important?▼

Backlog prioritization using the MoSCoW method sorts items into Must, Should, Could, and Won't categories to establish clear trade-offs. This enforces explicit scope decisions by focusing on must-have outcomes for your current sprint.

What is the MoSCoW method for feature prioritization?▼

The MoSCoW method for feature prioritization categorizes requirements into Must have, Should have, Could have, and Won't have. It helps teams align on scope by enforcing clear categorization and an explicit Won't list to define project boundaries.

How do I define project scope for a product launch?▼

Project scoping defines boundaries by classifying features into Must, Should, Could, and Won't categories. This determines Must features for version one while marking less critical items accordingly, producing an effort distribution table for stakeholder alignment.

Can I use MoSCoW prioritization for sprint planning?▼

MoSCoW prioritization suits sprint planning by sorting backlog items into Must, Should, Could, and Won't buckets. It applies during product planning or backlog refinement to drive scope decisions and focus on must-have outcomes.

When should I use MoSCoW instead of other prioritization methods?▼

Use MoSCoW prioritization when all backlog items feel equally important and you need to establish clear trade-offs. It is ideal during product planning or project scoping to enforce explicit Won't lists and focus on must-have outcomes.

Related Skills

Explore More Product & Management Skills→
shafibabarshafibabar
1

moscow-prioritization

Categorize product requirements into Must, Should, Could, and Won't categories.

Community
Intermediate
C0ntr0lledCha0sC0ntr0lledCha0s
3

planning-sprints

Automate sprint planning and backlog refinement with prioritization frameworks.

Community
Intermediate
jc180105jc180105

Sprint Prioritizer

Prioritize sprint backlog items using RICE, MoSCoW, or Kano frameworks.

Community
Advanced
junchenghuojunchenghuo
3

product-roi-prioritization

Prioritizes product features by ROI scoring matrix into Must/Should/Could/Won't tiers.

Community
Intermediate