English companion article · Published

Brief for an output

The episode compares Claude Chat with Claude Cowork, then discusses how to describe work for the latter. A deliverable-oriented brief needs a clear outcome and enough context to judge whether it is complete. “Help with this project” leaves more room for misunderstanding than naming the document, spreadsheet or other output you need.

Understand the capabilities together

The chapter sequence covers local files, persistent memory, connectors, Skills, Projects, browser control and scheduled tasks. Their value becomes clearer when you consider how they support a repeatable process. Files supply material, reusable instructions describe how to handle it, and connections make other sources or actions available.

The video also includes basic setup and a section on controlling computer work from a phone. Watch the relevant demonstration before applying a feature to your own environment; the interface and available capabilities can change.

Keep judgement in the workflow

The closing discussion covers safety and risks alongside practical uses. For repetitive business work, start with a process whose output you know how to review. Explain the boundaries, inspect the result and improve the brief when something is missing. The important measure is whether the finished work serves its purpose, rather than how many capabilities you enabled.

← Explore all articles & videos