u/MedimCounty

[ Removed by Reddit on account of violating the content policy. ]

Get these seven things right, in this order, and Cowork will be 10x more powerful for your workflow.

Context files before plugins

Cowork doesn't know who you are, what you do, or how you communicate. Without context, every plugin output is generic. Create three markdown files first:

• about-me.md name, role, company, communication style, timezone
• brand-voice.md words you use, words you avoid, example sentences that sound like you, topics you cover
• current-projects.md active work with deadlines, blockers, and links

Point Cowork to a folder containing these files. Every response is personalized before you install a single plugin.

Time investment: 30 minutes. Payoff: every interaction from that point forward.

The meta-prompt that prevents 90% of mistakes

Before running any task, prime Cowork with this:

You are my executive assistant. You have access to my computer and 
all connected tools. Always show me your plan before executing. Ask 
clarifying questions if anything is ambiguous. Never delete, move, or 
modify files without explicit approval.

This stops Cowork from going rogue on your filesystem. It forces plan-first execution, so you catch errors before they happen.

Save it as a global instruction. You should never have to type it again.

One workflow,

Pick one recurring task that takes 20+ minutes and build that workflow first. Run it for a full week. Refine it. Then add the second.

My recommendation for your first workflow: meeting prep.

I have a meeting with [NAME] from [COMPANY] in 30 minutes. 
Research them, find recent news, pull any previous email 
conversations, and give me a one-page briefing.

That one workflow saved me more time than the other four combined. It's also the one that makes you look prepared on every call without doing any of the prep yourself.

The folder structure that scales

Flat folders break at scale. Use this:

cowork-workspace/
├── context/ (about-me, brand-voice, projects)
├── successful-examples/ (your best emails, posts, proposals)
├── current-tasks/ (active deliverables)
└── references/ (standard operating procedures, style guides, templates)

The successful-examples folder is the one most people skip. Drop your best 5 to 10 emails, your highest-performing LinkedIn posts, your best client proposals. Cowork reverse-engineers your patterns instead of guessing your style.

Plugins in priority order

With context in place, plugins actually work. Install in this order:

1. Productivity task management, scheduling, workflow automation. Foundation layer.
2. Your industry-specific plugin marketing, sales, data, or whatever matches your daily work.
3. A custom plugin you build yourself tell Cowork: "I want to create a plugin for [your most repetitive task]. Interview me about the workflow, then build the plugin file." Takes 15 minutes. Saves hours.

Skip everything else until these three are running smoothly.

Scheduled tasks

Plugins and workflows run when you tell them to. Scheduled tasks run whether you remember or not.

Start with one: a daily morning briefing that checks your calendar, flags important emails, and lists your top priorities. Set it for 6am. By the time you sit down with coffee, your day is already organized. You didn't open Gmail. You didn't check Slack. Cowork already triaged everything.

The review loop that makes it better

Every Friday, spend 10 minutes reviewing what worked and what didn't. Update your context files. Tweak your workflows. Add new examples to your successful-examples folder.

Cowork gets better the more it knows about you. It only learns if you feed it.

Context files first. Then the meta-prompt. Then one workflow. Then plugins. Then scheduled tasks.

1. Context over prompts

Stop writing long prompts. Start building a file layer:

• _MANIFEST.md controls what the agent reads first
• about-me.md holds your identity
• brand-voice.md defines your tone
• working-style.md sets your rules

Generic output disappears once the agent has real context to work from.

2. Global instructions

Most people leave this blank. Set rules like:

• Always read the manifest first
• Ask before executing
• Show a plan
• No filler

Even a lazy one-line prompt produces usable output when the global instructions do the heavy lifting.

3. Scope what the agent reads

More context does not mean better output. It means worse output.

Tell the agent what to read, what to ignore, and when to load files. Most failures happen here.

4. Define done

"Help me organize files" is not a task.

A task is: folder structure, naming format, output log, edge cases handled. Treat the agent like a contractor with a spec, not a collaborator reading your mind.

5. Ask for a plan before execution

One line in your global instructions: "Show plan before execution."

This prevents most mistakes before they happen.

6. Handle uncertainty explicitly

Tell the agent what to do when it doesn't know:

• If unsure, flag it
• If unclear, verify before proceeding
• If there's a conflict, mark it needs-review

It stops guessing. You stop cleaning up after it.

7. Batch work

Don't run five sessions for five tasks. Run one session that processes, analyzes, reports, and drafts the email. Faster, cheaper, and the context stays coherent across steps.

8. Use subagents

Tell the agent to use subagents and tasks run in parallel. Work that takes 40 minutes serially takes 10.

9. Schedule recurring work

Weekly reports, daily summaries, competitor tracking. Set it up once and the agent runs it while you're not there.

10. Stack plugins

Combine data tools with sales tools. Stack marketing analysis alongside content generation. One workflow, multiple execution layers.

11. Build reusable skills

Create named workflows: "Write article", "Analyze data", "Generate report." One command triggers a full execution sequence you've already defined. You stop rebuilding the same thing from scratch.

12. Keep everything in files, not memory

Files give you control, repeatability, and scale. Memory gives you randomness. Everything worth keeping lives in your file layer.

13. Take the permissions seriously

Cowork can move files, rename data, and automate live systems. Set it up with the same care you'd give any process touching production.

14. Revise, don't redo

Most people say "rewrite this" or "do it again." That's the slowest way to work with Cowork.

Say instead:

• "Revise only section 2 for clarity"
• "Improve the intro, keep the structure"
• "Tighten the language, remove filler"

The agent reuses existing context instead of starting from zero. Output is faster, token use drops, and quality stays consistent.

15. Force output formats

If you don't specify a format, the agent decides. That's where messy results come from.

Always define:

• File type: .docx, .csv, .md
• Structure: headings, bullets, tables
• Length: word count or sections
• Style: concise, detailed, or executive summary

Example: "Deliver as a structured report with headings, bullet points, and a final summary. No filler."