moscow-prioritization

Categorize requirements into Must, Should, Could, and Won't tiers using the MoSCoW framework.

9|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/pantheon-org/tekhne --skill moscow-prioritization-pantheon-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moscow-prioritization
Source: https://github.com/pantheon-org/tekhne/tree/main/skills/project-mgmt/moscow-prioritization
Command: npx skills add https://github.com/pantheon-org/tekhne --skill moscow-prioritization-pantheon-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps teams deterministically categorize and prioritize product requirements using the MoSCoW framework, ensuring alignment with release constraints and preventing scope creep.

Core Features & Use Cases

  • Requirement Categorization: Assigns requirements to Must, Should, Could, or Won't tiers using a decision tree.
  • Scope Management: Facilitates MVP definition, release sequencing, and stakeholder conflict resolution.
  • Use Case: A product team needs to define the scope for their next release under a tight deadline. They use this Skill to categorize all proposed features, ensuring that only essential items are marked as 'Must' and that the total effort aligns with the team's capacity.

Quick Start

Use the moscow-prioritization skill to create a workshop draft for prioritizing requirements.

Frequently Asked Questions about moscow-prioritization

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

FAQPage Schema
How do I prioritize requirements for an MVP using the MoSCoW method?

The MoSCoW framework categorizes requirements into Must, Should, Could, and Won't tiers to deterministically define MVP scope. It applies a decision tree to sequence releases, resolve stakeholder conflicts, and rebalance backlogs under tight deadline constraints.

How do I manage scope creep when defining release scope under tight deadlines?

Manage scope creep under tight deadlines by categorizing requirements into MoSCoW tiers, ensuring only essential items are marked as Must. This prevents scope creep by validating the prioritized backlog against release timelines and team capacity constraints.

Can I use MoSCoW prioritization to resolve stakeholder conflicts over the product backlog?

Yes, you can use MoSCoW prioritization to resolve stakeholder conflicts by deterministically assigning requirements to Must, Should, Could, or Won't tiers. This structured categorization applies a decision tree to objectively rebalance the backlog under constraints.

Does MoSCoW prioritization validate total effort against release timelines and team capacity?

MoSCoW prioritization requires validation of categorized requirements against release timelines and team capacity. It applies effort balancing rules to ensure that the total effort of prioritized Must and Should tiers aligns with available team capacity.

What is the best way to sequence product releases when facing backlog constraints?

The best way to sequence product releases under constraints is applying the MoSCoW framework to categorize requirements into Must, Should, Could, and Won't tiers. This deterministic prioritization rebalances the backlog and aligns scope with release timelines.