PLN-DEC-01Tier IIPlanning & Decomposition

Task Prioritisation & Budget Control

Explicitly score, order, and budget sub-tasks so the agent spends resources where they produce the most value.

Runtime: DecideAgentOps: Operate & MonitorSee on the matrix →
TASK PRIORITISATION & BUDGET Task Queuecandidate work Scoreimpact ·urgency · cost Rankordered queue Executetop item Budget Check$ · tokens ·timeExplicit scoring beats first-come-first-served round-robin.
In Plain English

This page is the complete instruction page for one pattern called "Task Prioritisation & Budget Control." It explains the problem this pattern solves, the idea behind the solution, when you should (and should not) use it, and what happens afterward, both the good effects and the costs.

This matters because building AI agents is not just about making them clever. It is also about making them safe and predictable. Following a well-tested pattern like this one helps avoid common mistakes, and shows you exactly which safety rules and regulations it connects to, listed under "Standards Mesh" on this page.

Context

Agents doing many things at once (inbox triage, research, monitoring) need to allocate attention. Without explicit prioritisation, they round-robin or get stuck on low-value work.

Problem

Implicit prioritisation produces low-value busyness.

Forces

  • Thoroughness vs focus
  • User-perceived progress vs actual value

Solution

Score candidate tasks on impact × urgency × cost, with weights reflecting user or organisational preference. Maintain a ranked queue; execute in order; re-score on new information. Track and cap cumulative token/$ budget per goal.

Placement

Where this pattern acts in the two lifecycles

Runtime Cognitive
01Perceive
02Reason / Plan
03Decide
04Act
05Observe
06Reflect / Learn
07Terminate

03 Decide. Tool / route / next-action selection. 7 of 61 catalogue patterns act at this stage.

AgentOps Lifecycle
01Design & Scope
02Build & Integrate
03Evaluate & Red-Team
04Deploy
05Operate & Monitor
06Iterate & Adapt
07Decommission

05 Operate & Monitor. Runtime telemetry, drift detection. 18 of 61 catalogue patterns act at this stage.

Stages and counts from the catalogue data. The Runtime lens is the loop the agent runs each turn; the AgentOps lens is the lifecycle the team runs the agent through. See the Matrix for every pattern at each stage.

Applicability

  • Agents juggling multiple concurrent tasks
  • Email, Slack, monitoring agents
  • Research assistants

Anti-Patterns

  • First-come-first-served queuing
  • No budget ceiling

Consequences

  • +Resource efficiency
  • +Explicit tradeoffs exposed to user
  • −Scoring function needs tuning