Aglet

Prioritize Slices From an Oversized Agent Request

Prioritizing oversized scope means selecting the smallest slice that reduces the most important uncertainty. Rank candidate slices by decision leverage, dependency, evidence readiness, urgency, and review cost. Keep broad discovery behind a concrete outcome so the queue remains immediately actionable.

Decide where the work belongs

  1. Rank decision leverage

    For each candidate slice, state the decision it informs, the uncertainty it removes, and the downstream work it unlocks. Prefer a slice that can rule in or out a material path. Keep descriptive or optional work lower until the primary decision is clearer.

  2. Assess dependencies and cost

    Record required sources, owners, context, comparisons, and review effort for each slice. Identify blockers and overlapping evidence, then combine work only when the same bounded artifact serves both decisions. Avoid ordering several dependent slices as if they could finish independently.

  3. Set the queue

    Choose first slice, deferred slice, clarification request, or stop with owner, evidence cutoff, output, and acceptance trigger. Set a review point for widening scope. Do not accept a queue item whose success depends on answering every related question at once.

What to carry forward

Return an ordered scope queue where each slice names decision leverage, evidence, dependencies, owner, output, and widening trigger. The first item should have a finite stopping condition. Mark the order provisional when urgency, dependency ownership, or evidence readiness is unsupported.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow