MoSCoW Task Prioritizer AI Prompt

MoSCoW prioritization prompt: prioritize with Must, Should, Could, Won't using this AI prompt. Perfect for projects, launches, and overwhelming lists.

The prompt

Role: You are a project manager who uses the MoSCoW method to bring order to overloaded plans.

Context: I have a big list of tasks or features and no idea what is truly required vs. nice-to-have. I need a ruthless sort before I commit to deadlines.

Task: Sort my items using MoSCoW.
My items: [ITEM_LIST]
The goal/project: [PROJECT_GOAL]
The deadline: [DEADLINE]
Resources available: [RESOURCES]

Definitions to apply:
- Must have: without this, the project fails
- Should have: important but the project survives without it
- Could have: nice if time permits
- Won't have (this time): explicitly parked, no guilt

Deliver:
1. All items sorted into the four MoSCoW buckets with one-line reasons
2. A reality check: given my deadline and resources, flag Must-haves that don't fit and suggest what to demote
3. A "minimum viable" cut line: the smallest set that still succeeds
4. Won't-have items parked with a suggested revisit date each
5. The 3 questions I should ask stakeholders before finalizing

Format: Four sections with clear headings. Practical, deadline-aware tone.

Constraints: Must-haves cannot exceed 60% of items — if they do, force-rank. Every Won't needs a revisit date, not a vague "later." Be honest about what the deadline allows.

Variables to fill in

Replace each [variable] in the prompt with your own details:

[ITEM_LIST] [PROJECT_GOAL] [DEADLINE] [RESOURCES]

Example input

ITEM_LIST: user login, payment integration, dark mode, referral program, admin dashboard, email notifications...; PROJECT_GOAL: MVP launch; DEADLINE: 6 weeks; RESOURCES: 2 developers

How to use this prompt

Define the project goal crisply first — 'must' is meaningless without it. Share the sorted list with stakeholders; the Won't column prevents scope creep better than any argument.

Tips for the best results

Write the cut line down and defend it — scope creep starts with 'just one more'.
Revisit Could-haves only after all Musts are demonstrably done.
Celebrate shipping the Musts; perfection is the enemy of launched.