moscow-prioritization
Installation
SKILL.md
Purpose
Guide requirements engineers through the MoSCoW prioritization method to categorize all requirements into four clear buckets -- Must Have, Should Have, Could Have, and Won't Have -- with explicit definitions and allocation guidelines. This is the simplest defensible prioritization framework and works best for timeboxed delivery.
This is not "High/Medium/Low" with different labels. The key distinction is that MoSCoW ties directly to delivery commitments: Must Haves define the minimum usable subset, and Won't Haves are explicit scope exclusions, not "maybe later."
Key Concepts
The Four Categories
| Category | Definition | Commitment |
|---|---|---|
| Must Have (Mo) | Non-negotiable for this timebox. Without these, the delivery is a failure. | Guaranteed delivery |
| Should Have (S) | Important but not critical. The system is usable without them, though painful. | Expected delivery -- included unless something goes wrong |
| Could Have (Co) | Desirable but not important. Nice-to-have features that improve user experience. | Delivered only if time permits |
| Won't Have (W) | Explicitly excluded from this timebox. Not forgotten -- consciously deferred. | Not delivered this timebox; may be reconsidered later |