Aglet

Triage an Agent Task Missing Verification Steps

A task without a verification plan cannot distinguish completed work from a plausible draft. Triage should identify the behavior or decision that must be checked, the evidence needed, who reviews it, and what failure means. Keep implementation scope separate from proof obligations.

Establish what is happening

  1. Name the expected outcome

    Write the behavior, data state, document, or recommendation that should exist after the task, including relevant boundaries and exclusions. State what must remain unchanged. Replace broad success words with observable conditions a reviewer can inspect.

  2. Inventory proof inputs

    List fixtures, queries, screenshots, logs, comparisons, acceptance examples, and human review needed to check the outcome. Record source, time, revision, owner, and expected result. Mark evidence that is unavailable or only supports context rather than verification.

  3. Set failure and closure

    Define how a failed check is recorded, which result blocks acceptance, and what remains provisional. Name the reviewer, evidence format, and stopping condition. Preserve the task request beside the plan so later scope changes do not erase its proof obligations.

What to carry forward

Return a verification-gap brief with expected outcome, unchanged boundaries, checks, evidence owners, failure handling, reviewer, and stopping condition. Triage is complete when acceptance can be judged from observable results. Keep the task unready when proof depends on an unstated assumption or unavailable owner.

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