Capstone: Automate Your Workflow

You’ve learned the interface, mastered file operations, connected your tools, and absorbed the tips that make Cowork click. Time to put it all together.

🔄 Quick Recall: From the tips lesson, the three patterns that matter most: instructions.md for persistence, checkpoints for control, and specific prompts for quality. You’ll use all three in this capstone.

This lesson doesn’t introduce new concepts. Instead, you’ll build a real automation — something that saves you actual time starting this week.

Step 1: Pick Your Automation Target

Look at your last work week. Which tasks had these properties?

• Repetitive — you did it last week, you’ll do it next week
• Pattern-based — it follows similar steps each time
• Time-consuming — takes 15+ minutes manually
• Low-creativity — doesn’t require deep original thinking (data processing, formatting, compiling)

Here are common candidates by role:

Pick one. Just one.

✅ Quick Check: What three properties make a task a good automation candidate? (Repetitive, pattern-based, time-consuming)

Step 2: Document Your Current Process

Before automating, write down exactly what you do now. Be specific. Here’s an example for a weekly status report:

My current process (manual):
1. Open Slack #product-team and scroll through the week's messages (5 min)
2. Open Jira and check which tickets moved to Done this week (5 min)
3. Open my notes folder and read my daily standup notes (5 min)
4. Open Google Docs and create a new document (2 min)
5. Write the summary, manually pulling from all three sources (15 min)
6. Format it, add the metrics table, proofread (8 min)
7. Share it with my manager via email (2 min)

Total: ~42 minutes

Your process is your automation blueprint. Cowork can replace steps 1-6 entirely.

Step 3: Build the Workflow

Create an instructions.md in your project folder (if you haven’t already). Then write your automation prompt.

Here’s the weekly status report automation:

Read instructions.md first.

Then create this week's status report:

1. Read all .md files in the "standup-notes/" subfolder from this week
   (files named YYYY-MM-DD.md)

2. Create a file called "status-report-2026-03-19.md" with:

   ## Weekly Status Report — March 14-19, 2026
   **Team:** Product Engineering
   **Author:** [my name]

   ### Highlights
   - Top 3 accomplishments this week (from standup notes)

   ### Metrics
   | Metric | This Week | Last Week | Change |
   |--------|-----------|-----------|--------|
   | Tasks completed | [count] | [from last report] | +/- |
   | Bugs fixed | [count] | [from last report] | +/- |
   | PRs merged | [count] | [from last report] | +/- |

   ### Blockers
   - Any blockers mentioned in standup notes + proposed solutions

   ### Next Week
   - Key priorities for next week (from most recent standup)

3. Keep the tone professional but concise. My manager skims these.

Show me the plan before writing.

Step 4: Test and Refine

Run the workflow. Review the output. It won’t be perfect on the first try — that’s expected.

Common refinements:

• “The highlights section is too detailed — just 1 sentence each”
• “You missed the blockers from Wednesday’s notes”
• “Add a section for team shoutouts”
• “Change the date format to March 14-19 instead of 2026-03-14”

Each refinement makes the template better. After 2-3 iterations, save the final prompt as a file:

# Save as: weekly-report-prompt.md
[your refined prompt here]

Next week, you start with: “Read instructions.md and weekly-report-prompt.md, then create this week’s status report.” Three minutes instead of 42.

Step 5: Add Scheduling (Optional)

Cowork supports scheduled, recurring tasks. If your automation runs on a fixed schedule:

1. Set up the task using the scheduling feature in Cowork
2. Choose the frequency (weekly, daily, etc.)
3. Cowork will run it automatically and you review the output

Not all workflows need scheduling. But for things like “every Monday morning, compile last week’s data” — it’s a game-changer.

Course Review: What You’ve Learned

Let’s recap the eight lessons:

Your Cowork Reference Card

Keep these patterns handy:

Starting a session:

Read instructions.md first, then: [task]

File safety:

Don't delete anything. Create new files instead of modifying originals.

Complex tasks:

Do this in phases. Show me each phase before moving on.

Feedback loop:

Almost there. Change X and add Y. Keep everything else.

What to Do This Week

1. Run your capstone workflow at least once with real data
2. Refine the prompt based on what needs adjusting
3. Save the final prompt as a reusable template file
4. Next week, run it again — notice how much faster it is

After one week, you’ll have a real sense of how much time Cowork saves. That’s when most people go looking for more things to automate.

Keep Going

Want to go deeper? Here’s where to head next:

• Cowork Skills & Plugins Mastery — Build custom skills, create plugins, master the MCP ecosystem (coming soon)
• Claude Code Mastery — For developers who want Claude’s coding capabilities
• Prompt Engineering — Master the fundamentals that make every AI tool work better
• Browse 1,000+ AI skills in our skill library — ready-to-use prompts for any task

Key Takeaways

• The best automation targets are repetitive, pattern-based tasks that take 15+ minutes
• Document your manual process first — it becomes your automation blueprint
• Build and test each step, then combine into a full workflow
• Save refined prompts as template files for reuse
• One well-tested workflow beats ten untested ones — start with one, expand from there

Congratulations on finishing the course. Go claim your certificate.