Day 3 of 14 Β· Claude Cowork Challenge
Your First Task
β± 6 min
π Beginner
You've installed Claude Desktop and set up your work folder. Now it's time to actually use Cowork. Today you'll give Claude your first real task, learn how to review its plan before it runs, watch it work with full transparency, and practice course-correcting mid-task.
The pattern you'll learn today β describe, review, run, refine β is the core loop of working with Cowork. Master it, and you'll use it for everything.
Every Cowork task follows this pattern: describe, review, execute, receive.
Describing your task clearly
The quality of Claude's work depends heavily on how you describe the task. This isn't about magic prompt formulas β it's about being specific the way you'd be specific with a human colleague.
Be clear about the output. Don't just say "help me with my files." Say "organize the files in my project folder into subfolders by file type, and create a README listing what's in each folder."
Give context. If you're asking for a report, mention who it's for and what decisions it should support. If you're organizing files, explain the logic you want.
Define success. What does "done" look like? A spreadsheet? A sorted folder? A summary document? Tell Claude what you expect to receive.
Here's the difference:
Vague: "Clean up my files."
Specific: "I have 30 files dumped in my work folder β a mix of PDFs, images, Word docs, and spreadsheets. Sort them into subfolders by type (documents, images, data), rename them with a consistent format (YYYY-MM-DD-description), and create an inventory spreadsheet listing every file with its original name, new name, and folder."
Knowledge Check
What makes a good task description for Claude Cowork?
A
Including step-by-step instructions for every single action Claude should take
B
Using technical jargon so Claude understands you're serious
C
Keeping it as short as possible β one sentence max
D
Being specific about the desired output, giving context, and defining what success looks like
You don't need to micromanage the steps β Claude figures those out. But you do need to be clear about what you want delivered. Specific outputs, relevant context, and a definition of "done" give Claude what it needs to plan and execute effectively.
Reviewing Claude's plan
Here's something that sets Cowork apart from other AI tools: Claude shows you its plan before executing.
When you give Claude a complex task, it doesn't just start working blindly. It breaks the task into steps, shows you its reasoning, and waits for your approval on significant actions. This transparency is by design β you're always in the loop.
A typical plan looks like this:
1. First, I'll scan the folder to see what files exist
2. Then I'll categorize them by file type
3. I'll create the subfolder structure
4. I'll move and rename each file
5. Finally, I'll generate the inventory spreadsheet
Always review the plan. This is your chance to catch misunderstandings before any work happens. If Claude's plan doesn't match what you expected, correct it now β not after it's reorganized 200 files the wrong way.
Safety tip: For tasks that modify existing files, tell Claude "don't delete anything" unless deletion is specifically what you want. Claude respects this instruction.
I have a messy folder with about 30 files β reports, screenshots, spreadsheets, random PDFs. Can you organize them into a clean structure and give me an inventory of everything?
I'll organize your folder. Let me first scan what's there...
I found 32 files. Here's my plan:
**1. Create folder structure:**
- /documents (Word docs, PDFs)
- /spreadsheets (Excel, CSV files)
- /images (PNG, JPG, screenshots)
- /other (anything that doesn't fit)
**2. Move and rename files:**
- Each file gets renamed to: YYYY-MM-DD-description.ext
- I'll use the file's last modified date for the date prefix
- Descriptions will be based on the file content or existing name
**3. Create inventory:**
- inventory.xlsx with columns: Original Name, New Name, Folder, File Type, Size, Date
I won't delete any original files β just move and rename them. Does this plan look right, or would you like me to adjust anything?
Perfect, but put CSVs in the spreadsheets folder too.
Got it β CSVs will go in /spreadsheets alongside the Excel files.
Starting now...
Done. 32 files organized:
- /documents β 14 files
- /spreadsheets β 8 files (including 3 CSVs)
- /images β 7 files
- /other β 3 files
π inventory.xlsx is in the root of your work folder with the full breakdown.
β» Replay conversation
Knowledge Check
Why does Claude show you its plan before executing a task?
A
Because it can only execute one step at a time and needs permission for each
B
Because it's required by law to get user consent
C
So you can review the approach, catch misunderstandings, and course-correct before work begins
D
Because it needs your help to figure out the steps
Transparency is a core design principle of Cowork. By showing its plan, Claude lets you verify the approach before any files are modified. This prevents mistakes, saves time, and keeps you in control of the process.
Watching Claude work
Once you approve the plan, Claude starts working. And unlike a chat response that just appears all at once, Cowork shows you what it's doing in real time.
You'll see Claude's reasoning as it works β which files it's reading, what decisions it's making, which sub-tasks it's executing. This isn't just a loading bar. It's a transparent window into the agent's thought process.
This matters for two reasons:
Trust. You can see that Claude is doing what you asked, not something unexpected. If it starts heading in the wrong direction, you catch it immediately.
Learning. Watching Claude work teaches you how it approaches problems. You'll start to understand its strengths, its patterns, and where it might need clearer instructions next time.
I'm watching you work and I see you're putting the quarterly-report.pdf in /other instead of /documents. Why?
Good catch β I miscategorized that one. The file name didn't match my initial pattern for reports. Let me move it to /documents right now.
Done. quarterly-report.pdf is now in /documents and renamed to 2025-12-15-quarterly-report.pdf.
This is exactly why it's helpful to watch the process. Want me to continue, or would you like to review any other placements before I finish?
β» Replay conversation
Course-correcting mid-task
You're not a passive observer. At any point during execution, you can interrupt Claude and give new instructions. This is one of Cowork's most powerful features.
Common mid-task corrections:
- "Wait β skip the image files, I'll handle those myself."
- "Actually, use the client name instead of the date for the file prefix."
- "Stop. Let me review what you've done so far before you continue."
- "Add a 'priority' column to that spreadsheet you're building."
Claude handles interruptions gracefully. It pauses, acknowledges your correction, adjusts its approach, and continues. You don't lose progress β it picks up where it left off with the new instructions incorporated.
Think of it like working with a junior colleague. You give them a task, check in on progress, and redirect when needed. The difference is that Claude doesn't get frustrated when you change your mind.
Knowledge Check
What happens when you interrupt Claude mid-task with a correction?
A
Claude finishes the current task first, then applies your correction
B
The correction is saved but applied only to future tasks
C
Claude pauses, acknowledges the correction, adjusts its approach, and continues from where it left off
D
Claude starts the entire task over from scratch
Cowork is designed for mid-task course correction. Claude can pause, incorporate your feedback, and resume without losing progress. This makes the workflow collaborative β you're guiding the work, not just waiting for it to finish.
Final Check
What is the core workflow loop when using Claude Cowork?
A
Describe the task, review Claude's plan, run it, and refine as needed
B
Type, wait, copy, paste
C
Upload files, select a template, click generate
D
Prompt, regenerate, prompt again
The describe-review-run-refine loop is how you work with Cowork. You describe what you want, review Claude's plan, let it execute while watching and course-correcting, and refine the output. It's a collaborative workflow, not a one-shot generation.
π―
Day 3 Complete
"Describe clearly, review the plan, watch the work, and redirect when needed β that's the Cowork loop."
Tomorrow β Day 4
Working with Files
You'll learn how Claude creates professional documents β Word, Excel, PowerPoint, and PDF β with real formatting, formulas, and layouts.