What should a pilot brief specify before generation begins?

Use this checklist to make the pilot's development question and decision rules explicit before requesting generated material.

- Name the agent behaviour the pilot must establish. - Define the process boundary and excluded decisions. - State which tools and permissions the agent will have. - Choose case variations that could change the correct action. - Identify who will adjudicate disputed expected outcomes. - Specify which failures require revision before expansion. - Define the evidence needed to justify a broader scope.

The pilot should support a decision, rather than simply produce material that looks plausible. For a professional services transfer from delivery to billing, the question might be whether the agent can distinguish billable completion from an unresolved acceptance condition. The brief should state how that distinction will be judged.

Keep case selection separate from result selection. Choosing only successful runs after seeing the agent's behaviour would weaken the conclusion. Agree the evaluation set and treatment of invalid cases before comparing outcomes.

A useful first step is a brief that a process owner and an agent engineer can both review. Their agreement helps prevent business ambiguity from becoming an integration problem later.