moscow

Categorize project requirements into Must have, Should have, Could have, and Won't have.

106|14|Updated Jan 10, 2026

Search Tags:#project management #decision making #requirements #prioritization #scope #moscow

Ready to run

npx skills add https://github.com/neurofoo/agent-skills --skill moscow-neurofoo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: moscow
Source: https://github.com/neurofoo/agent-skills/tree/main/moscow
Command: npx skills add https://github.com/neurofoo/agent-skills --skill moscow-neurofoo

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps clarify priorities and define scope by categorizing items into Must have, Should have, Could have, and Won't have, preventing scope creep and ensuring focus on critical elements.

Core Features & Use Cases

Categorization: Sorts any list of items into the four MoSCoW categories.
Scope Definition: Clearly outlines what is essential, important, desirable, and out of scope for a project or task.
Use Case: When planning a new software feature set, use MoSCoW to determine which features are critical for the Minimum Viable Product (MVP), which are important for a strong launch, and which can be deferred to later releases.

Quick Start

Use the moscow skill to categorize the following items for a new website launch: User authentication, blog section, advanced search, user profiles, and admin dashboard.

Frequently Asked Questions about moscow

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

FAQPage Schema

How do I use the MoSCoW method to prioritize project requirements?▼

The MoSCoW method categorizes project requirements into Must have, Should have, Could have, and Won't have buckets to facilitate scope definition. This structured framework ensures clear understanding of project criticalities and constraints.

What is the best way to define scope and prevent scope creep for a new feature set?▼

To define scope and prevent scope creep, categorize items using the MoSCoW framework to distinguish what is essential, important, desirable, and out of scope. This clarifies priorities and ensures focus on critical elements.

How do I determine which features are critical for a Minimum Viable Product?▼

To determine critical MVP features, sort your feature list into Must have, Should have, Could have, and Won't have categories. This categorization identifies what is essential for the MVP versus what can be deferred to later releases.

Can I use MoSCoW prioritization for resource allocation discussions?▼

Yes, MoSCoW prioritization facilitates resource allocation discussions by sorting tasks into Must have, Should have, Could have, and Won't have categories. This ensures a clear understanding of project criticalities and constraints.

Does MoSCoW scope definition work for any list of project tasks?▼

MoSCoW scope definition works by sorting any list of items into the four MoSCoW categories. It clearly outlines what is essential, important, desirable, and out of scope for a project or task.