Aglet

Learn From Missing Verification Plans

Learning from missing verification plans means making proof obligations part of task design. Preserve the claim that lacked a check, the boundary case that exposed the gap, and the acceptance wording that resolved it. Turn those lessons into examples without imposing irrelevant checks.

Keep the lesson for the next incident

  1. Classify plan failures

    Group incidents by vague outcome, absent unchanged behavior, missing boundary, unavailable evidence, unowned reviewer, no failure handling, scope change, or missing closure. Keep one task claim and acceptance consequence for each class. Distinguish a plan defect from a result that is intentionally provisional.

  2. Keep proof exemplars

    Retain compact plans showing outcome, preserved behavior, normal and boundary cases, expected results, evidence, reviewer, failure path, and stopping condition. Include a deliberately provisional result with its revisit trigger. Update examples when task families or review standards change.

  3. Review recurrence and ownership

    Assign owners for task design, evidence collection, and acceptance review as needed. Sample new agent tasks on a defined cadence and track missing proof fields. Reopen investigation for repeated generic checks, unowned failures, or acceptance decisions unsupported by retained evidence.

What to carry forward

Close the learning record with plan-failure classes, proof exemplars, owners, and a trigger for missing or generic acceptance evidence. Preserve provisional outcomes as explicit behavior. The durable result is task design that makes proof visible before work is called complete.

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