A first-run checklist for your AI crew

Before assigning important work, verify the entire path from account access to a readable local file. Each check answers a different setup question.

Work through these checks

1. Work engine

confirm the selected CLI is detected and authorized. Record the evidence or the unresolved question before moving on.

2. Role

read the working guide and required tools. Record the evidence or the unresolved question before moving on.

3. Workspace

verify the exact folder or sandbox mode. Record the evidence or the unresolved question before moving on.

4. Brief

name one input, output and acceptance rule. Record the evidence or the unresolved question before moving on.

5. Result

open the physical file and compare it with the source. Record the evidence or the unresolved question before moving on.

Put the checklist to work

A five-line meeting note is a useful first input because every extracted action can be checked manually.

Keep the checklist beside the task brief and the actual output. Mark a check complete only after inspecting the relevant file, setting or event. If a required check cannot run in the current environment, describe that gap and choose an appropriate next review rather than substituting a confident summary.

A boundary to remember

A sample task shown in the browser demo does not satisfy any real execution check.

For the corresponding controls and troubleshooting steps, read the desktop help guide. These checks are a practical review aid; adapt them to the specific source material and intended use of your deliverable.