LEVEL 3 — WORKFLOWS

The Cowork Cookbook

Copy-paste prompts and complete setups from people who use Cowork every day. No theory — just what works.

Before You Start These workflows assume you've completed the Cowork Beginner setup — or at minimum: Claude Desktop installed, a workspace folder selected, and Gmail + Calendar connected. If you haven't done that yet, start there and come back.

Six Workflows

Who This Is For

CEO or founder managing multiple roles. You have 90 seconds before your day explodes. You need to queue work from anywhere, not just at your desk.

The Setup

Organized Workspace Folders

Create: Active Work → Today's Work. This is where Claude queues tasks and outputs pile up. You review from this single folder.

Gmail + Calendar Connectors

Connect your email and calendar. Claude can now read incoming messages and your day's schedule to prioritize intelligently.

Dispatch Connected on Phone

Install Claude on your phone. You can message Claude from Dispatch at 6 AM and watch the queue build. Desktop handles execution while you shower.

The Prompts

Go through my emails, prioritize the tasks for me that are most important, and organize them. Draft emails where you can to the ones that I should be responding to.
Plan out content for Substack. Make a branded HTML with candidate ideas. This month I want to speak about [TOPIC]. Search the web, look for compelling stories I may want to cover, and organize that as a content calendar.
Organize my Downloads folder. Segment [PROJECT] relevant files into that folder. Within the [PROJECT] folder, ensure you have relevant files categorized by customer and task.

What Claude Produces

Prioritized email drafts ready to send. A content calendar in HTML with story ideas, sourced and themed. Files organized by project and task type — all before you sit down at your desk.

Why It Works Dispatch lets you fire 5 tasks from your phone in 5 minutes while your Mac executes in parallel. You queue, walk away, review outputs over coffee. No waiting. No context switching.
Make It Yours Replace email triage with your biggest morning time sink. Swap 'Substack' for your platform. Change 'Downloads' to whatever folder collects clutter. The pattern works for any role that has repeatable morning work.
Level Up: Turn This Into a Skill If you're running this dispatch every morning, stop copy-pasting the prompt. Tell Claude: "Build me a skill called 'morning-dispatch' that runs my 5 morning tasks. Read my current dispatch prompt and convert it into a reusable skill with my email rules, content platform, and folder structure baked in." Once it's a skill, one sentence triggers the whole thing — and it gets smarter as your MEMORY.md grows. New to skills? See Cowork Advanced, Section 1. Scheduled tasks? Section 6.

Inspired by Christian Pean MD, Techy Surgeon

Who This Is For

Anyone starting with automation. You don't need ten tasks. Start with three. Let them run for a week and feel the difference before you add anything else.

The Setup

Gmail + Calendar Connectors

Connect your email and calendar so Claude can read them as part of each scheduled task.

Scheduled Tasks Enabled

Make sure Cowork has permission to run scheduled tasks. This happens during setup, but verify in Settings if tasks don't fire.

The Three Tasks

1

Morning Briefing (Daily 8 AM)

Summarize my unread emails by priority. Check today's calendar. Create a prioritized task list with talking points for each meeting. Output as an HTML file in my workspace.
2

Meeting Prep (Daily, 30 min before first meeting)

Review the agenda and attendees for my next meeting. Pull any recent email threads with these people. Draft 3 talking points and 2 questions to ask.
3

Evening Debrief (Daily 6 PM)

Summarize what I accomplished today based on sent emails and calendar events. Flag anything that needs follow-up tomorrow. Keep it under one page.

What Claude Produces

A morning HTML briefing with your day's priorities. Pre-meeting prep with talking points and questions. End-of-day summary with follow-ups flagged and ready for tomorrow.

Why It Works Start small. Three tasks. One week. You'll feel the difference before you add anything else. These three cover: morning focus, meeting readiness, and end-of-day clarity. That's the foundation.
Keep Your Mac Awake Scheduled tasks only run while your Mac is on and Claude Desktop is open. If your Mac is asleep at the scheduled time, the task runs when you wake it.
Make It Yours Swap meeting prep for your recurring prep type. Change debrief time to your cadence. Cron examples: 0 9 * * 1-5 for weekdays at 9 AM, 30 8 * * 1 for Mondays at 8:30 AM.
Level Up: Wrap Your Tasks in a Skill You've got the scheduled tasks running — now make them smarter. Tell Claude: "Look at my 3 scheduled tasks. Build a skill called 'daily-ops' that combines the briefing, meeting prep, and debrief into one system. Include my email priority rules, meeting types, and output preferences so I don't have to re-specify them." A skill gives your scheduled tasks a shared brain — consistent formatting, your preferences baked in, and better outputs over time.

Inspired by Christian Pean MD, Techy Surgeon

Who This Is For

Consultant, lawyer, agency professional. You produce the same type of deliverable repeatedly. You want consistent quality and fast turnaround.

The Setup

Project Folder with Template

Add your report template (.docx). Include 2 strong past examples as reference. Add the client brief and any reference docs. Include project instructions: "Include executive summary. Never exceed 15 pages. Structure: summary → findings → recommendations → next steps → appendix. Output as .docx."

The Prompt

The client just sent their brief — it's in the project folder. Read the brief, compare it to our template and past examples, then ask me 3-4 clarifying questions before you generate the full report as a Word doc.

What Claude Produces

A templated Word document with executive summary, findings, recommendations, next steps, and appendix. All formatted to your style, based on the template and examples you provided.

Why It Works Template + examples stay permanently loaded in the project. Scoped memory means Claude improves with each report. The third report is noticeably better than the first.
Make It Yours Swap template for proposals, SOWs, legal memos, case studies. Add letterhead .docx for auto branding. Key: give Claude 2-3 strong examples of what 'good' looks like for your domain.
Level Up: Build a Deliverable Skill If you produce the same type of document more than twice, it should be a skill. Tell Claude: "Build me a skill called 'client-report' that generates [DOCUMENT TYPE] from a brief. Read my template and the last 3 reports I produced. Bake in the structure, formatting rules, and quality checks. The skill should ask me clarifying questions before generating, just like a good junior analyst would." Now one sentence — "run client-report for Acme" — produces a first draft that matches your standards.

Inspired by Ruben Hassid, How to AI

Who This Is For

Founder prepping for investor meetings. Analyst sizing a market. Sales rep researching accounts. Anyone who needs research they can actually trust.

What Makes This Different

Most people ask Claude to 'research X' and get a generic summary with no sources. This approach uses a recursive research loop — the same methodology behind dedicated research skills that produce 15-30 page cited dossiers. The difference is structure: Claude decomposes the research into sub-questions, probes sources in priority order, tracks confidence on every claim, and separates evidence from inference.

The Research Loop

Step What Happens
Probe Search sources in priority order: official site → social channels → reviews → press/third-party
Decompose Break each section into 3-6 sub-questions. No claims without citations.
Recurse For each sub-question, inspect sources, write a mini-brief with citations + confidence
Synthesize Combine mini-briefs into the final section. Resolve conflicts between sources.

Evidence Rules

1

Every Claim Cited

Inline citations with source, date accessed, and confidence (High / Medium / Unconfirmed). No naked claims.

2

Three-Tier Separation

Company-stated claims vs. third-party corroboration vs. inference. Each labeled explicitly.

3

No Speculation

If not publicly disclosed, write "No public disclosure found as of [date]" instead of guessing.

The Prompts

Person Research:

Research [PERSON NAME] at [COMPANY]. I'm meeting them for [PURPOSE]. Probe their LinkedIn, company site, talks, podcasts, and social media. Decompose into: career timeline, current role and priorities, communication style, personal interests, and fit with my ask. Cite every claim with source and confidence level. Separate evidence from inference. Output as a Word doc with an executive brief I can read in 5 minutes before the meeting.

Company Research:

Research [COMPANY] — [WEBSITE]. I'm evaluating them as [CONTEXT: competitor / partner / investment]. Probe their site first (product, pricing, about, blog, terms), then social, reviews, and press. Decompose into: business model, product offering, target customers, GTM motion, partner ecosystem, competitive landscape (8-12 players), and momentum in the last 24 months. Cite everything. No speculation on revenue or internal metrics. Output as a Word doc with executive summary.

Industry/Market Research:

Research the [INDUSTRY] market. Probe industry associations, research firms, company filings, government sources, and trade press. Decompose into: market sizing (TAM/SAM/SOM), value chain, competitive landscape, customer segments, technology trends, regulation, risks, and strategic opportunities. Present conflicting estimates as ranges. Cite every figure. Output as a Word doc with a 'So What' section at the end.

What Claude Produces

A 10-25 page Word document with inline citations, confidence scores, a source pack (12-25 annotated links), comparison tables, and an executive summary. The output quality depends on the prompt structure — the recursive loop and evidence rules are what separate this from a generic 'research X' request.

Why It Works The recursive loop forces depth. Decomposing into sub-questions prevents Claude from writing generic summaries. Source priority order ensures you're building from primary sources, not regurgitating blog posts. Confidence scoring tells you what to trust and what to verify yourself.
Make It Yours These prompts are starting points — customize the decomposition list for your domain. Add 'focus on [SPECIFIC ANGLE]' to narrow the research. Drop existing research into the project folder for Claude to build on. For recurring research (weekly competitive intel, regulatory monitoring), convert to a scheduled task. Install the person-research, company-research, or industry-research skills for the full automated version.
Level Up: Build Your Own Research Skill The prompts above are the manual version. The real power is building a research skill that encodes YOUR methodology permanently. Tell Claude: "Build me a research skill using this framework: probe sources in priority order (official site → social → reviews → press), decompose each topic into 3-6 sub-questions, recurse through each sub-question with citations and confidence scoring (High / Medium / Unconfirmed), then synthesize into a final report. Separate evidence from inference. Include a source pack with 15-25 annotated links. Output as a .docx with an executive brief on page one." Once built, saying "research [person/company/market]" triggers a 15-30 page cited dossier — no prompt engineering required. For recurring intel (weekly competitor scans, regulatory monitoring), pair the skill with a scheduled task.

Research methodology by Steve Gustafson

Who This Is For

Anyone with data who needs visuals fast. You have the data. You don't care about the technical implementation. You want a dashboard you can share.

The Setup

Drop CSV/Excel into Project Folder

That's it. No plugins, no connectors, no special configuration. Just add your data file to the project folder.

The Prompt

Read the data file in my project folder. Create an interactive HTML dashboard with: a summary metrics bar at the top, dropdown filters for [COLUMN1] and [COLUMN2], a trend chart showing [METRIC] over time, and a sortable data table below. Use a dark theme. Make it a single HTML file I can share with anyone.

What Claude Produces

A single-file HTML dashboard with Chart.js, dropdown filters, summary cards, responsive design. Fully interactive. Share via email or Slack. Works in any browser.

Why It Works One file, no dependencies, opens in any browser, shareable via email or Slack. Claude handles the Chart.js code, responsive layout, and filter logic. You get dashboards in minutes instead of hours.
Make It Yours Change column names and metrics to match your data. Add 'include a comparison to last month/quarter' for period-over-period. Request chart types: bar for categories, line for trends, scatter for correlations. Combine with a scheduled task for recurring dashboards that update weekly.
Level Up: Make This a Scheduled Task If your data updates regularly (weekly exports, monthly reports), stop doing this manually. Tell Claude: "Create a scheduled task that runs every Monday at 9 AM. It should read the latest CSV in my [PROJECT] folder, generate an updated dashboard with the same layout and filters as last time, and save it as an HTML file with this week's date. Compare to last week's numbers and flag anything that changed more than 10%." Now your dashboard rebuilds itself — and you get anomaly alerts for free.

Who This Is For

Executive managing multiple domains. Anyone who wants the complete automated intelligence system. Start with three tasks. By week four, you have a personal operating system.

The Pattern

This isn't a single workflow — it's what happens when you combine the previous five into a system. Start with the Essential Three (Workflow 2). Add one domain-specific task per week. By week four, you have a personalized operating layer that handles your morning briefing, meeting prep, recurring research, deliverable production, and end-of-day wrap-up — without you re-explaining anything.

The Graduated Rollout

1

Week 1: Deploy the Essential Three

Morning briefing, meeting prep, evening debrief. Just these. Get comfortable with the rhythm. Notice what changes in your day.

2

Week 2: Add One Domain Task

Pick from the menu below based on your role. One task only. Don't add more until you see the value from this one.

3

Week 3: Add a Second Domain Task

By now you see which automations actually save time vs. create noise. Add the second one based on what worked.

4

Week 4+: Customize Based on What's Useful

You now have a personalized operating system. Iterate weekly. Remove what doesn't work. Add what does.

Domain Task Menu

Deal Pipeline Pulse

Scan emails for stale sales conversations. Flag deals going cold. Alert on inactivity over 2 weeks.

Weekly Competitive Intel

Monitor 3-5 competitor sites for pricing, features, blog, and hiring changes. Deliver as a weekly summary.

Customer Success Threads

Compile customer emails and tickets by priority. Flag escalations. Summarize by issue type.

Regulatory Monitoring

Scan relevant government sources weekly for policy changes. Alert on changes that affect your business.

Invoice Cleanup

Scan emails for invoices. Extract amounts, vendors, dates. Flag items over your threshold for review.

The Setup Prompt

Interview me about my professional life. Ask me about my roles, priorities, VIP contacts, deal stages, recurring meetings, and communication preferences. Then generate a comprehensive context file and suggest 5 scheduled tasks based on what you learn.

What Claude Produces

A complete context file + recommended scheduled task library tailored to your actual work. Over time, scoped memory learns your patterns and the outputs get sharper. By week 8, Claude knows your priorities better than most people around you.

"The question is not 'how do I do more?' but 'how do I offload the mechanical work so my limited attention goes to decisions that require judgment?'"
— Christian Pean MD, Techy Surgeon
Why It Works The graduated approach prevents overwhelm. Starting with 3 tasks instead of 10 means you actually stick with it. Adding weekly lets you evaluate what's useful vs. what creates "slop at scale." The interview prompt builds a context file that makes every future task better.
The 'Slop at Scale' Warning Every output requires human review. The value is in first-draft quality and organization — not blind automation. If you're spending more time editing outputs than you saved, that task isn't working. Remove it and try a different one.
Make It Yours The domain tasks above are examples — replace them with whatever recurring work eats your time. The interview prompt is the key unlock: it builds a context file tuned to YOUR work, not generic templates. Run the interview again every quarter as your priorities shift.
Level Up: Generate Your Entire Skill Library The interview prompt above is your launchpad. After Claude builds your context file, take it one step further: "Based on the context file you just built, generate 3-5 custom skills for my most repetitive workflows. Each skill should include my preferences, output format, and quality checks. Then suggest which ones should also be scheduled tasks with recommended timing." This turns a one-time interview into a permanent operating system. Each skill runs on one sentence. Each scheduled task runs on autopilot. The context file ties them all together.

Inspired by Christian Pean MD, Techy Surgeon

Pick One. Start Today.

You don't need all six. Pick the workflow closest to your daily pain. Set it up. Run it for a week. Then come back for the next one.

← Cowork Beginner Cowork Advanced →
Prompting Guide → People I Learn From →