Use Work when the output is a finished artifact or outcome and the task has several dependent steps. Keep the scope explicit, give only the files and apps needed, and define what must be reviewed before the task is considered done.
1. Write the outcome and acceptance criteria before naming tools
Write the deliverable as a noun plus a measurable finish condition—for example, “a 10-slide board brief with every market claim cited.” This gives Work a target it can test instead of an open-ended instruction.
2. Add only the files, project context and connected apps needed for this job
Attach the brief, source files and only the connected apps that contain necessary evidence. Excluding unrelated sources reduces search noise and makes it easier to audit where each conclusion came from.
3. Use Plan mode or ask for a short plan when the task has several branches
Before execution, inspect the proposed sequence for missing dependencies, duplicated work and actions that should require approval. If a branch can be answered independently, let it run separately and bring only the result back.
4. Let Work gather, analyze and create, but stop at approvals or uncertain assumptions
Allow autonomous reading, synthesis and drafting, but keep external writes, purchases, account changes and uncertain assumptions behind an approval point. When evidence is missing, require a question or an explicit “not verified” note instead of a guess.
5. Review the final artifact against the original acceptance criteria and source evidence
Re-open the acceptance criteria and verify them one by one against the artifact. Spot-check cited facts in the original source, confirm requested format/length, and keep unresolved items in a visible limitations section.
Use Work to complete this outcome: [deliverable]. Context you may use: [files/apps/project]. Constraints: [scope, date, audience]. Before acting, show a short plan. Ask before any external write or irreversible action. Finish with the deliverable plus a checklist showing how each acceptance criterion was met.
Using Work for a one-question task; giving it every connected source; letting the task expand without a stop condition; accepting a polished document without checking the underlying evidence; mixing several unrelated deliverables into one run.
Finish check
You can explain what sources were used, which actions were taken, what was not verified, and why the final artifact satisfies the requested outcome.