Introduction to Claude Cowork ｜ Lesson 04「Claude Cowork に最初のタスクを手渡す（Hand Claude Cowork your first task）」
出典: Anthropic Academy ／ 2026-07-04
日本語ナレッジ（完全版・本文の自然な全訳）
所要時間の目安：15分
このレッスンで学べること（Learning objectives）
このレッスンを終えると、次のことができるようになります。
- Cowork タスクを端から端まで歩ける：委任（delegation）→タスク途中の軌道修正（mid-task steering）→最終レビュー
- Cowork の確認質問（clarifying questions）に、より良い出力を生む形で答えられる
- Claude が誤った方向に進みかけたとき、軌道修正できる
一つのタスクを最初から最後まで見る
この動画は、一つのリアルな仕事を委任から成果物まで通しで見せます——プロンプト、Claude が投げる確認質問、ユーザーが途中でルートを変える瞬間、そして最後の完成した成果物。そのリズムに注目してください。チャットボットにプロンプトを打つというより、優秀な同僚に手短にブリーフィングし、その同僚がタスクに潜り込んで、何かを完成させて戻ってくる——それに近い感覚です。
キーテイクアウェイ（Key takeaways）
- Claude はコミットする前に確認します。 自明でないタスクの多くは、まず一つ二つの確認質問から始まります。この質問は、仕事を始める前に文脈のギャップを埋めるための手段であって、邪魔な摩擦ではありません。
- 途中で軌道修正できます。 Claude が誤った方向に進んでいたら、割って入ってください。終わるまで待って最初からやり直す必要はありません。
- 完成した成果物こそが「アーティファクト」であり、チャットではありません。 Claude はあなたのコンピュータ上のファイルに変更を加えます。最後のあなたの仕事は、同僚の仕事をレビューするのと同じ要領で、それをレビューすることです。
最初のタスクを委任する
前のレッスンでタスクを一つ選びました。いよいよ、それがあなたの手を離れるときです。Cowork を開き、そのタスクの文脈が宿るフォルダに向け、関連する文脈を持つコネクタをオンにし、プロンプトを書きます。
良い Cowork プロンプトは、3つのことをします。
- 成果物を名指しする（Names the deliverable）。 「1ページのブリーフ」「QBR 用のスライド1枚」「候補ごとに注記を付けたランキングリスト」。形式や長さの具体は、再生成（regenerate）の手間を省きます。
- 入力を名指しする（Names the inputs）。 どのフォルダ、どのチャンネル、どの期間、どのアプリケーションか。Cowork は、あなたが向けた文脈の質までしか良くなりません。
- 仕事を仕上げるのに Claude が必要とする追加の具体・ニュアンスを名指しする。 「昨年 Q3 に開設した3つの新拠点も織り込んだうえで、ベース／ベスト／ワーストの各シナリオを見たい」。この一文は、求める出力の種類を Claude に方向づけ、Claude が気づかないかもしれないあなたの専門知見という鍵を提供します。
（このレッスンにはインタラクティブ教材が続き、Cowork プロンプトの例を組み立てます。）
英語原文
Estimated time: 15 minutes
Learning objectives — By the end of this lesson you'll be able to:
- Walk a Cowork task end-to-end: through delegation, mid-task steering, and final review
- Respond to Cowork's clarifying questions in a way that produces better output
- Course-correct when Claude heads in the wrong direction
Watch one go end-to-end — This video walks through a single, real piece of work from delegation to deliverable: the prompt, the clarifying questions Claude asks, the moment the user reroutes mid-task, and the finished result at the end. Notice the rhythm — it's less like prompting a chatbot and more like briefing a smart colleague who's about to disappear into a task and come back with something done.
Key takeaways
- Claude asks before it commits. Most non-trivial tasks start with a clarifying question or two. The questions are how Claude closes context gaps before the work starts, not friction in the way.
- You can steer mid-task. If Claude is heading in the wrong direction, jump in. You don't have to wait for it to finish and start over.
- The finished deliverable is the artifact, not the chat. Claude makes changes to the files on your computer. Your job at the end is to review it the way you'd review a colleague's work.
Delegate your first task — You picked a task in previous lessons. Now is when it leaves your plate. Open Cowork, point it at the folder where the context for the task lives, turn on any connectors that hold relevant context for the task, and write your prompt.
A good Cowork prompt does three things:
- Names the deliverable. "A one-page brief," "a slide for the QBR," "a ranked list with notes per candidate." Specifics about format and length save you a regenerate.
- Names the inputs. Which folder, which channels, which date range, which application. Cowork is only as good as the context you point it at.
- Names additional specifics or nuances Claude would need to get the job done. "I want to see base, best, and worst case scenarios that also account for the 3 new locations we opened in Q3 last year." That sentence directs Claude on the type of output you're looking for, and provides key insights from your expertise that Claude might not see.
(An interactive follows to build an example Cowork prompt.)
固有動画 字幕（逐語・yt:Lbml7IuGJYw）
Claude Cowork meets you where your work happens and allows you to delegate complete tasks to Claude. If it's on your computer, Claude can find and edit it. If it's in the cloud, Claude connects through services like Google Drive, Notion, and Slack. If it's in the browser, Claude is there, too, through Claude in Chrome. Describe what you need done and Claude does it. You can watch it work, steer when it matters, or step away and come back to the results.
Claude Cowork is generally available in the Claude desktop app on macOS and Windows for Pro, Max, Team, and Enterprise users. To get started, open Claude desktop and click the Cowork tab. In a regular Claude chat, you work with Claude step-by-step. In Cowork, you hand off tasks and Claude handles the rest while you focus on other work.
First, give Claude access to a folder on your computer. Select the folder directory or project you want Claude to operate in. It asks permission before making changes to your file system. Claude can now read, create, and edit files in that folder directly. You can favorite the folders you go to most or select multiple folders to connect to disparate data sources.
Second, connect your tools. Cowork supports connectors that link Claude to services. These let Claude pull context from where your work already lives.
Third, if you've set up Claude in Chrome, Cowork can use it for browser-based tasks, reading web pages, extracting data from sites, and navigating across tabs.
Under settings, you can also click the Cowork tab and set global instructions that apply to every session, like context about your role or directions to create files as Word docs instead of markdown. One thing to keep in mind, your Cowork sessions are stored locally on your device. And the desktop app needs to stay open while Claude is working on a task.
Let's start with something really simple to show how Claude can work directly with your local files. You have a downloads folder full of months of accumulated files, PDFs, spreadsheets, screenshots, and duplicates. Just a ton of random stuff. You connect it and tell Claude, "Organize my downloads folder. Scan the contents and propose a plan. Categories to create, how files should be sorted, naming conventions to apply, and files to flag for review or deletion. Show me the plan before making changes."
Claude comes back with a proposed structure. Documents, spreadsheets, presentations, images, and a duplicates folder collecting redundant copies. It suggests date-based naming conventions and flags for files that look like duplicates for review. You look at the flagged duplicates and notice two of them are actually different versions you want to keep. You tell Claude, "Move those two to a review folder instead of deleting them and go ahead with the rest of the plan." Claude adjusts and continues on.
As Claude works, you can watch the progress in the top right corner. You can click on each task to see details or ask questions. Files actually move on your machine. When it finishes, your downloads folder is organized, renamed, and cleaned up.
In a regular chat, Claude could describe how to organize your files. In Cowork, Claude does it. That's the core Cowork loop. Claude proposes a plan and waits for your approval before taking action. You can adjust the plan, redirect the approach, or tell Claude to skip certain steps. Once you approve, Claude executes directly in your file system. Start with tasks that have clear boundaries like this one, and always review what Claude produces. You're delegating the work, not the judgment.