prioritise

Prioritise tasks

Take a set of tasks and produce a defensible priority order.

Steps

1. If no task list was provided, ask for it. If a task-planner breakdown already exists (or is stored via the memory connector), offer to use that.
2. Choose a method appropriate to the situation and state which you're using:
   • Impact vs effort — quick wins first, then big bets; default for mixed backlogs.
   • Urgent / important (Eisenhower) — when deadlines and importance conflict.
   • Value vs risk — when delivery confidence varies a lot. Ask the user if they have a preference; otherwise pick and explain.
3. Score each task briefly against the chosen axes — keep the reasoning short and visible, not a black box.

Output

Return:

• A ranked list, highest priority first, each with a one-line rationale.
• A short do-now / do-next / defer grouping for quick scanning.
• Any assumptions you made (e.g. inferred deadlines), so the user can correct them.

If the memory connector is available, offer to save the prioritised order so it can be revisited and adjusted later.