Create intermediate Works with: Any AI

MoSCoW Scope Negotiation

Table output Has example

Cut scope with agreement.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Prioritize requirements with MoSCoW. List of requirements: [REQUIREMENTS]. Fixed constraints (date, budget, team): [CONSTRAINTS]. Business goals: [GOALS].

Classify each as Must (the release fails without it), Should (important but a workaround exists), Could (nice to have), or Won't this time. For each, state the reasoning and the consequence of leaving it out. Apply a rule of thumb: Musts should take no more than about 60 percent of capacity, leaving room for risk; compute the effort split with my estimates and show the arithmetic.

Produce: a table: Requirement | Class | Reason | Effort | Dependencies | Risk if dropped. Flag Musts that look like Shoulds disguised. Create a negotiation script (80 words) for a stakeholder who says everything is a Must, with the questions "What happens on launch day if this is missing?" and "Who is harmed?". Add a plan for revisiting the list weekly.

Present the final list as four groups with the total effort of each group and the percentage of capacity, and state the minimum viable release as the Musts only, with the date it would allow.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Requirements (effort in days): R1 login 5 (Must); R2 invoice list 8 (Must); R3 export to CSV 3 (Should); R4 dark mode 6 (Could); R5 multi-currency 12 (Should); R6 API 10 (Won't this time).
Capacity 40 days. Musts: 5 + 8 = 13 days (32.5 percent of capacity).
Shoulds: 3 + 12 = 15; Musts + Shoulds = 28 days (70 percent), leaving 12 days for risk.
Could: 6 days fits only if risk is low.
Script: "What happens on launch day if this is missing? Who is harmed?"
Challenge: R5 multi-currency looks like a Should disguised as a Must for one customer; test with sales.
Revisit the list weekly. Minimum viable release: R1 and R2.

• moscow