Aglet

Learn From Repeated Unclear Agent Briefs

Learning from unclear briefs means improving the questions and examples that shape future work. Record the phrase or omission that caused divergent execution, the clarification that resolved it, and the output needed by the reviewer. Turn those observations into guidance without hiding legitimate task differences.

Keep the lesson for the next incident

  1. Classify ambiguity patterns

    Group incidents by unclear decision, missing source, undefined boundary, conflicting instruction, unstated authority, vague output, or absent stop rule. Keep one concrete example and its consequence for each class. Distinguish a writing defect from a real policy choice that needs an owner.

  2. Keep brief exemplars

    Retain short before-and-after briefs for recurring task types, with decision, scope, evidence, constraints, deliverable, and stop condition visible. Annotate why each field matters. Update exemplars when a new source, review role, or output requirement changes the workflow.

  3. Review recurrence and ownership

    Assign an owner for brief quality and a reviewer for authority or policy questions. Sample new tasks on a defined cadence and track which fields still require clarification. Reopen investigation when the same ambiguity recurs or when a template encourages unsupported assumptions.

What to carry forward

Close the learning record with ambiguity patterns, annotated exemplars, owners, and a review trigger tied to clarification frequency or divergent execution. Keep policy decisions separate from wording guidance. The durable result is a more reviewable task contract, not a promise that every future brief needs identical language.

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