Define proof of completion for file-producing tasks

A completion message is weaker evidence than an artifact that opens and passes checks. Define the proof before starting so the teammate knows what to report.

Start with a small handoff

Select a role by its working guide and deliverables, then verify the connected AI tool and workspace. Keep the first run small enough that you can inspect every output. The desktop needs to stay running while work executes. Marketplace sign-in, model access and file-generation tools are separate setup requirements; a success in one does not prove the others are ready.

Inputs for this workflow: The output format, acceptance criteria and available validation tools.

Work through the task

1. Require exact output paths.
2. Request a list of checks actually performed.

A brief you can adapt

Create the requested document and report its filename, sections produced and validation performed. List any checks that could not run in this environment.

The filenames above are examples. Replace them with your actual inputs and destination before submitting the task.

Review the deliverable

Open the original file and repeat the checks most important to its intended use.

Where this approach can fail

Do not accept a renamed file or fabricated test result as proof that the task finished.

For the related desktop setup, see first task.