8421bit/niopd-skills/niopd-st-moscow

Claude Code and agent skill by 8421bit/niopd-skills

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Applies MoSCoW prioritization method to categorize requirements by importance. Use for scope negotiations, release planning, or stakeholder alignment on priorities.

Install

npx vskill@latest install 8421bit/niopd-skills/niopd-st-moscow

SKILL.md

MoSCoW Prioritization Skill

This skill applies the MoSCoW method to systematically categorize requirements, helping teams focus on what's truly essential.

Theoretical Foundation

Origin

MoSCoW was developed by Dai Clegg at Oracle in 1994 as part of the Dynamic Systems Development Method (DSDM). The name is an acronym for the four priority categories.

The Four Categories
CategoryMeaningCriteria
Must HaveCritical–no viable product withoutNon-negotiable
Should HaveImportant but not vitalHigh value, not critical
Could HaveDesirable if time permitsNice to have
Won't HaveExplicitly excluded (this time)Out of scope
Key Principle

At most 60% of effort should go to Must Haves, ensuring buffer for the unexpected.

When to Use
  • Release planning
  • Scope negotiation
  • Stakeholder alignment
  • Resource allocation
  • MVP definition

Instructions

Step 1: Gather All Requirements

List all features/requirements from:

  • PRD
  • Backlog
  • Stakeholder requests
  • User feedback
Step 2: Define "Must Have" Criteria

Clarify with stakeholders:

  • What makes something absolutely critical?
  • What cannot be compromised?
  • What breaks the product if missing?
Step 3: Categorize Each Item

For each requirement:

  • Must: Would the product fail without this?
  • Should: Is it very important but survivable without?
  • Could: Is it nice to have if time permits?
  • Won't: Should we explicitly exclude this?
Step 4: Validate Must Haves

Challenge each "Must Have":

  • Is this truly essential?
  • What would happen without it?
  • Could we ship and add later?
Step 5: Check 60% Rule

Calculate effort distribution:

  • Must Haves: ≤60% of effort
  • If over: Re-evaluate what's truly "Must"
Step 6: Document and Communicate

File path: 02-reports/[YYYYMMDD]-moscow-priorities-v0.md

Format:

markdown
## Must Have
-[Requirement]: [Rationale]
## Should Have
-[Requirement]: [Rationale]
## Could Have
-[Requirement]: [Rationale]
## Won't Have (This Release)
-[Requirement]: [Why excluded]

Output Specifications

  • File Naming: [YYYYMMDD]-moscow-priorities-v0.md
  • Location: 02-reports/
  • Template: references/moscow-template.md

Related Skills

  • niopd-st-rice: Quantitative prioritization
  • niopd-ur-kano: Satisfaction-based categorization
  • niopd-pd-roadmap: Roadmap planning
  • niopd-pm-release: Release planning

Security

  • Security scanPassed, 90 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
5

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/8421bit/niopd-skills/niopd-st-moscow/badge)](https://verified-skill.com/skills/8421bit/niopd-skills/niopd-st-moscow)

Something wrong with this skill or its page? Tell us.