docs: complete Cowork documentation v1.0 (Phase 2)

- Create comprehensive Cowork docs (23 files in cowork/) - 6 guides: overview, getting started, capabilities, security, troubleshooting - 60+ ready-to-use prompts across 4 categories - 5 step-by-step workflows - Reference materials: cheatsheet, FAQ, comparison, glossary - Integrate Perplexity research (P0/P1/P2) - Exact error messages with solutions (VPN, Chrome host, context limits) - Competitive analysis (vs Copilot/Gemini/ChatGPT/Apple Intelligence) - Enterprise validation (TELUS, Rakuten, Zapier stats) - OCR accuracy benchmarks (97% field, 63% line-item) - Token budget planning per task type - Document critical limitations - VPN incompatibility (#1 community issue) - Context limit reality (165K vs 200K theoretical) - Platform constraints (macOS only) - Usage limits and pricing (Pro $20, Max $100-200) - Update central files - README.md: detailed Cowork section with tables - VERSION: 3.9.6 → 3.9.7 - machine-readable/reference.yaml: add cowork_reference entry - machine-readable/cowork-reference.yaml: new LLM-optimized index (~1.5K tokens) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-01-20 11:23:43 +01:00 · 2026-01-20 11:23:43 +01:00 · c2de35caba
commit c2de35caba
parent 360e5203f6
27 changed files with 7304 additions and 12 deletions
--- a/cowork/workflows/README.md
+++ b/cowork/workflows/README.md
@ -0,0 +1,100 @@
+# Cowork Workflows
+
+> **Step-by-step tutorials for common Cowork tasks**
+
+---
+
+## Available Workflows
+
+| Workflow | Description | Time | Difficulty |
+|----------|-------------|------|------------|
+| [File Organization](file-organization.md) | Clean up messy folders | 15 min | Beginner |
+| [Expense Tracking](expense-tracking.md) | Receipts → Excel report | 20 min | Intermediate |
+| [Report Synthesis](report-synthesis.md) | Multi-doc → report | 25 min | Intermediate |
+| [Meeting Prep](meeting-prep.md) | Create briefing docs | 20 min | Intermediate |
+| [Team Handoff](team-handoff.md) | Dev ↔ Non-dev patterns | 30 min | Advanced |
+
+---
+
+## Workflow Structure
+
+Each workflow includes:
+
+1. **Use Case** — When to use this workflow
+2. **Prerequisites** — What you need before starting
+3. **Step-by-Step Instructions** — Detailed walkthrough
+4. **Example Prompts** — Copy-paste ready commands
+5. **Troubleshooting** — Common issues and solutions
+6. **Variations** — Adapting for different scenarios
+
+---
+
+## Quick Start
+
+### Before Any Workflow
+
+```bash
+# 1. Ensure workspace exists
+mkdir -p ~/Cowork-Workspace/{input,output}
+
+# 2. Backup important files
+cp -R ~/Cowork-Workspace/ ~/Cowork-Backup-$(date +%Y%m%d)/
+
+# 3. Clear previous work (optional)
+rm -rf ~/Cowork-Workspace/input/*
+rm -rf ~/Cowork-Workspace/output/*
+```
+
+### Workflow Checklist
+
+- [ ] Workspace folder ready
+- [ ] Input files in place
+- [ ] Backup if doing destructive operations
+- [ ] Cowork enabled in Claude Desktop
+- [ ] Folder access granted
+
+---
+
+## Choosing a Workflow
+
+```
+What do you need to do?
+│
+├─ Organize messy files?
+│   └─ → File Organization workflow
+│
+├─ Process receipts or expenses?
+│   └─ → Expense Tracking workflow
+│
+├─ Combine documents into a report?
+│   └─ → Report Synthesis workflow
+│
+├─ Prepare for a meeting?
+│   └─ → Meeting Prep workflow
+│
+└─ Work between technical and non-technical team members?
+    └─ → Team Handoff workflow
+```
+
+---
+
+## Tips for All Workflows
+
+### Be Explicit
+```
+❌ "Organize my files"
+✅ "Organize files in ~/Cowork-Workspace/input/ by type into subfolders"
+```
+
+### Review Before Approving
+Always read Cowork's execution plan before saying "proceed."
+
+### Start Small
+Test with a few files before processing hundreds.
+
+### Check Results
+Verify output before considering the task complete.
+
+---
+
+*[Back to Cowork Documentation](../README.md)*
--- a/cowork/workflows/expense-tracking.md
+++ b/cowork/workflows/expense-tracking.md
@ -0,0 +1,327 @@
+# Workflow: Expense Tracking
+
+> **Estimated time**: 20 minutes
+> **Difficulty**: Intermediate
+
+---
+
+## Use Case
+
+You have receipt photos, screenshots, or scanned documents and need to:
+
+- Extract expense data into a spreadsheet
+- Categorize expenses
+- Create totals and summaries
+- Track for reimbursement or accounting
+
+> ⚠️ **Important**: Claude excels at reading receipt **fields** (vendor, date, totals) but is weaker at **line-item extraction** from tables (63% accuracy vs 97% for fields). Always verify totals manually. Budget 30-50% of time saved for validation and error correction.
+
+---
+
+## Prerequisites
+
+- [ ] Cowork enabled with Chrome access (for receipt photos)
+- [ ] Receipt images (JPG, PNG) or PDFs
+- [ ] Workspace folder created
+
+---
+
+## Step-by-Step Instructions
+
+### Step 1: Prepare Receipts
+
+```bash
+# Create workspace structure
+mkdir -p ~/Cowork-Workspace/{input/receipts,output}
+
+# Copy receipts to workspace
+cp ~/Downloads/*.jpg ~/Cowork-Workspace/input/receipts/
+cp ~/Downloads/*.png ~/Cowork-Workspace/input/receipts/
+cp ~/Downloads/*.pdf ~/Cowork-Workspace/input/receipts/
+```
+
+**Tip**: Name files descriptively if possible (e.g., `2024-01-15-uber.jpg`)
+
+### Step 2: Review Receipt Quality
+
+Check image quality—Cowork uses OCR and works best with:
+- Clear, in-focus photos
+- Good lighting
+- Full receipt visible
+- Minimal glare/shadows
+
+### Step 3: Initial Extraction
+
+Start with a basic extraction:
+
+```
+Extract expense data from receipt images in ~/Cowork-Workspace/input/receipts/
+
+Create an Excel file with columns:
+- Date (YYYY-MM-DD format)
+- Vendor/Store
+- Amount (number only, no currency symbol)
+- Currency (3-letter code: USD, EUR, etc.)
+- Category
+- Payment Method (if visible: Cash, Credit, Debit)
+- Receipt Filename (for reference)
+
+Save to: ~/Cowork-Workspace/output/expenses.xlsx
+```
+
+### Step 4: Review Initial Results
+
+Open the Excel file and check:
+- Are dates correct?
+- Are amounts accurate?
+- Are vendors recognized correctly?
+- Any missing or garbled data?
+
+### Step 5: Request Corrections
+
+If there are issues:
+
+```
+Review the expense file you created.
+
+Corrections needed:
+- Row 3: Amount should be 45.99, not 4599
+- Row 7: Date should be 2024-01-15
+- Row 12: Vendor is "Starbucks" not "Slarbucks"
+
+Make these corrections and save.
+```
+
+### Step 6: Add Summaries
+
+Enhance the spreadsheet with analysis:
+
+```
+Enhance ~/Cowork-Workspace/output/expenses.xlsx with:
+
+Sheet 2 - "Category Summary":
+- Category
+- Total Amount
+- Number of Transactions
+- Percentage of Total
+
+Sheet 3 - "Monthly Summary":
+- Month
+- Total Amount
+- Transaction Count
+- Top Category
+
+Sheet 4 - "Vendor Summary":
+- Vendor
+- Total Spent
+- Number of Visits
+- Average Transaction
+
+Add formulas so summaries update automatically.
+Use [European/US] formula syntax.
+```
+
+### Step 7: Final Review
+
+```
+Create a final summary of the expense data:
+- Total expenses
+- Date range covered
+- Number of receipts processed
+- Any receipts that couldn't be fully extracted
+
+Save summary to ~/Cowork-Workspace/output/expense-summary.txt
+```
+
+---
+
+## Example Prompts
+
+### Basic Extraction
+```
+Extract expenses from receipts in ~/Cowork-Workspace/input/receipts/
+Columns: Date, Vendor, Amount, Category
+Save to ~/Cowork-Workspace/output/expenses.xlsx
+```
+
+### With Auto-Categorization
+```
+Extract expenses and auto-categorize:
+- Food & Dining: restaurants, cafes, grocery
+- Transportation: uber, lyft, gas, parking
+- Office: supplies, software, subscriptions
+- Travel: hotels, flights, rental cars
+- Other: everything else
+
+Save with categories to ~/Cowork-Workspace/output/categorized-expenses.xlsx
+```
+
+### With Tax Separation
+```
+Extract expenses with tax breakdown:
+Columns: Date, Vendor, Subtotal, Tax, Total, Category
+
+For receipts that show tax separately, extract it.
+For receipts without tax breakdown, put total in Total column, leave Tax blank.
+
+Add a summary showing total tax paid.
+```
+
+### Reimbursement Report
+```
+Create a reimbursement report from expenses in ~/Cowork-Workspace/output/expenses.xlsx
+
+Format as Word document with:
+- Employee Name: [Your Name]
+- Report Period: [Auto-detect from dates]
+- Itemized expenses table
+- Category subtotals
+- Grand total
+- Certification statement line for signature
+
+Save to ~/Cowork-Workspace/output/reimbursement-report.docx
+```
+
+---
+
+## Troubleshooting
+
+### OCR Can't Read Receipt
+
+**Cause**: Poor image quality, unusual font, or receipt damage
+
+**Solutions**:
+- Retake photo with better lighting
+- Try scanning instead of photographing
+- Manually enter data for problematic receipts
+
+```
+For receipts you couldn't read, add placeholder rows:
+- Date: MANUAL ENTRY NEEDED
+- Filename: [receipt filename]
+I'll fill in the details manually.
+```
+
+### Wrong Amounts Extracted
+
+**Common issues**:
+- Decimal point confusion (1500 vs 15.00)
+- Currency symbol included in number
+- Total vs subtotal confusion
+
+```
+Review all amounts in the expense file.
+Ensure:
+- Amounts are numbers only (no $ or € symbols)
+- Decimal places are correct (15.99 not 1599)
+- Use the TOTAL amount, not subtotal
+
+Show me any rows where you're uncertain about the amount.
+```
+
+### Categories Are Wrong
+
+```
+Recategorize expenses using these rules:
+- "Amazon" → Check item: Office if supplies, Personal if other
+- "Uber"/"Lyft" → Transportation (not Travel)
+- Coffee shops → Food & Dining (not Office)
+
+Update the spreadsheet with correct categories.
+```
+
+### Duplicate Entries
+
+```
+Check for duplicate expenses (same date, vendor, amount).
+Mark potential duplicates but don't delete.
+Add "Possible Duplicate" flag column.
+```
+
+---
+
+## Regional Settings
+
+### US/Canada
+```
+Use US format:
+- Dates: MM/DD/YYYY
+- Currency: USD/CAD
+- Formula separators: comma (,)
+```
+
+### Europe
+```
+Use European format:
+- Dates: DD/MM/YYYY
+- Currency: EUR
+- Formula separators: semicolon (;)
+```
+
+### Mixed Currencies
+```
+Handle multiple currencies:
+- Keep original currency column
+- Add "Amount USD" column with conversion
+- Use exchange rate as of receipt date
+- Note conversion rate in summary
+```
+
+---
+
+## Variations
+
+### Credit Card Statement Reconciliation
+```
+Compare extracted receipts to credit card statement in ~/Cowork-Workspace/input/statement.pdf
+
+Create reconciliation report showing:
+- Matched transactions
+- Statement entries without receipts
+- Receipts without statement entries
+- Amount discrepancies
+```
+
+### Monthly Expense Report
+```
+From expenses in ~/Cowork-Workspace/output/expenses.xlsx, create monthly report:
+
+Include:
+- Spending by category (pie chart data)
+- Comparison to previous month
+- Highest expense categories
+- Unusual transactions
+- Budget tracking (if budget provided)
+
+Save to ~/Cowork-Workspace/output/monthly-report.docx
+```
+
+### Team Expense Consolidation
+```
+Consolidate expense files from ~/Cowork-Workspace/input/team-expenses/
+(Multiple expense files from different team members)
+
+Create master spreadsheet with:
+- All expenses from all files
+- "Submitted By" column
+- Team totals
+- Per-person totals
+
+Save to ~/Cowork-Workspace/output/team-expenses.xlsx
+```
+
+---
+
+## Best Practices
+
+1. **Name receipt files well** — `YYYY-MM-DD-vendor.jpg` helps Cowork
+2. **Process in batches** — Don't do 200 receipts at once; do 20-30
+3. **Verify ALL totals** — OCR line-item accuracy is ~63%; always manually verify sums
+4. **Keep originals** — Don't delete receipt images until verified
+5. **Note uncertainties** — Ask Cowork to flag uncertain extractions
+6. **Budget for validation** — Plan 30-50% of "saved" time for error correction
+7. **Use Max for large batches** — Pro quota (~1.5h intensive) may not cover 50+ receipts
+
+---
+
+*[Back to Workflows](README.md) | [Cowork Documentation](../README.md)*
--- a/cowork/workflows/file-organization.md
+++ b/cowork/workflows/file-organization.md
@ -0,0 +1,262 @@
+# Workflow: File Organization
+
+> **Estimated time**: 15 minutes
+> **Difficulty**: Beginner
+
+---
+
+## Use Case
+
+You have a messy folder with mixed files—Downloads folder, project folder, or any disorganized collection. This workflow helps you:
+
+- Sort files by type, date, or project
+- Create logical folder structures
+- Generate organization reports
+- Clean up naming inconsistencies
+
+> ⚠️ **Set realistic expectations**: No independent benchmarks exist for AI file organization productivity. Vendor claims of "5x time savings" are marketing, not research. AI helps most with **routine categorization**; complex or ambiguous files still need human judgment.
+
+---
+
+## Prerequisites
+
+- [ ] Cowork enabled in Claude Desktop
+- [ ] Files to organize (can be any number)
+- [ ] Workspace folder created
+
+---
+
+## Step-by-Step Instructions
+
+### Step 1: Prepare Your Workspace
+
+```bash
+# Create workspace if needed
+mkdir -p ~/Cowork-Workspace/{input,output}
+
+# Copy files to organize (don't move originals yet)
+cp -R ~/Downloads/* ~/Cowork-Workspace/input/
+
+# OR for a specific folder
+cp -R ~/SomeMessyFolder/* ~/Cowork-Workspace/input/
+```
+
+**Important**: Copy first, don't move. This preserves originals until you're satisfied.
+
+### Step 2: Survey the Files
+
+Start a Cowork conversation and ask for an overview:
+
+```
+List all files in ~/Cowork-Workspace/input/ and show me:
+- Total count
+- File types present
+- Approximate breakdown by type
+- Any patterns in naming
+```
+
+Review this before proceeding. It helps you understand what you're working with.
+
+### Step 3: Choose Organization Strategy
+
+**Option A: Organize by Type**
+```
+Organize all files in ~/Cowork-Workspace/input/ by file type.
+
+Create these folders:
+- Documents (pdf, doc, docx, txt, md, rtf)
+- Spreadsheets (xls, xlsx, csv, numbers)
+- Images (jpg, jpeg, png, gif, svg, webp)
+- Videos (mp4, mov, avi, mkv)
+- Audio (mp3, wav, m4a, flac)
+- Archives (zip, rar, tar, gz, 7z)
+- Code (js, py, html, css, json, xml)
+- Other (everything else)
+
+Move files to appropriate folders.
+Save organization report to ~/Cowork-Workspace/output/organization-report.txt
+```
+
+**Option B: Organize by Date**
+```
+Organize all files in ~/Cowork-Workspace/input/ by date.
+
+Create year/month folder structure:
+- 2024/
+  - 01-January/
+  - 02-February/
+  - ...
+- 2025/
+  - 01-January/
+  - ...
+
+Use file modification date for sorting.
+Move files to folders.
+Create report in ~/Cowork-Workspace/output/date-organization.txt
+```
+
+**Option C: Organize by Project**
+```
+Analyze files in ~/Cowork-Workspace/input/ and organize by project.
+
+Identify projects based on:
+- Filename patterns
+- Content (read text files)
+- Related file groups
+
+Create a folder for each project identified.
+Put unclassifiable files in "Unsorted/" folder.
+Create project index in ~/Cowork-Workspace/output/project-index.md
+```
+
+### Step 4: Review the Plan
+
+Cowork will show you its planned actions. **Read carefully**:
+
+- Does the folder structure match your expectations?
+- Are file categorizations correct?
+- Is the scope appropriate?
+
+If something looks wrong, say:
+```
+Wait. Modify the plan:
+- [Your correction]
+```
+
+### Step 5: Execute and Verify
+
+If the plan looks good:
+```
+Proceed with the plan
+```
+
+After completion:
+```bash
+# Check the results
+ls -la ~/Cowork-Workspace/input/
+
+# Review the report
+cat ~/Cowork-Workspace/output/organization-report.txt
+```
+
+### Step 6: Apply to Original (Optional)
+
+If satisfied with the organization:
+```bash
+# Remove original messy folder (CAREFUL!)
+rm -rf ~/Downloads/*
+
+# Move organized files to original location
+mv ~/Cowork-Workspace/input/* ~/Downloads/
+```
+
+---
+
+## Example Session
+
+```
+USER: List all files in ~/Cowork-Workspace/input/
+
+COWORK: Found 247 files:
+- Documents: 45
+- Images: 120
+- Videos: 15
+- Archives: 22
+- Other: 45
+
+USER: Organize by type. Create folders for Documents, Images, Videos,
+Archives, and Other. Move files appropriately.
+Create report in ~/Cowork-Workspace/output/organization.txt
+
+COWORK: [Shows plan with 5 folders and file distribution]
+
+USER: Proceed
+
+COWORK: [Executes and reports completion]
+```
+
+---
+
+## Troubleshooting
+
+### "Permission denied" on some files
+
+```bash
+# Check file permissions
+ls -la ~/Cowork-Workspace/input/
+
+# Fix permissions if needed
+chmod 644 ~/Cowork-Workspace/input/*
+```
+
+### Files not categorized correctly
+
+Be more specific about rules:
+```
+Recategorize: Move .md files to Documents, not Code.
+Move .json files with "config" in name to Configuration folder.
+```
+
+### Hidden files being ignored
+
+```
+Also process hidden files (starting with .)
+Include them in the appropriate categories.
+```
+
+### Too many "Other" files
+
+Specify additional categories:
+```
+Create additional folders:
+- Fonts (ttf, otf, woff)
+- Installers (dmg, pkg, exe)
+- Data (json, xml, yaml)
+```
+
+---
+
+## Variations
+
+### Clean Filenames While Organizing
+
+```
+Organize by type AND standardize filenames:
+- Remove special characters
+- Replace spaces with hyphens
+- Convert to lowercase
+- Add date prefix (YYYY-MM-DD)
+```
+
+### Identify Duplicates
+
+```
+Before organizing, identify duplicate files.
+Create duplicates report in ~/Cowork-Workspace/output/duplicates.txt
+Group duplicates but don't delete any.
+Then organize unique files by type.
+```
+
+### Archive Old Files
+
+```
+Organize recent files (last 6 months) by type.
+Move older files to ~/Cowork-Workspace/input/archive/
+Create manifest of archived files.
+```
+
+---
+
+## Best Practices
+
+1. **Always copy first** — Work on copies until satisfied
+2. **Review the plan** — Don't auto-approve
+3. **Check the report** — Verify categorization accuracy
+4. **Start with small tests** — Test with 20 files before 2000
+5. **Keep backups** — Until you're confident in results
+6. **Budget for review** — Plan 30-50% of time for checking and fixing misfiles
+7. **Watch your quota** — Large batches (500+ files) consume significant tokens; Pro users may hit limits
+
+---
+
+*[Back to Workflows](README.md) | [Cowork Documentation](../README.md)*
--- a/cowork/workflows/meeting-prep.md
+++ b/cowork/workflows/meeting-prep.md
@ -0,0 +1,363 @@
+# Workflow: Meeting Preparation
+
+> **Estimated time**: 20 minutes
+> **Difficulty**: Intermediate
+
+---
+
+## Use Case
+
+You have an upcoming meeting and need to:
+
+- Research the company/people you're meeting
+- Compile relevant background materials
+- Create a briefing document
+- Prepare talking points and questions
+
+---
+
+## Prerequisites
+
+- [ ] Cowork enabled with Chrome access (for web research)
+- [ ] Any existing documents about the meeting/company
+- [ ] Clear understanding of meeting purpose
+
+---
+
+## Step-by-Step Instructions
+
+### Step 1: Set Up Workspace
+
+```bash
+# Create workspace for meeting prep
+mkdir -p ~/Cowork-Workspace/input/meeting-[name]
+mkdir -p ~/Cowork-Workspace/output
+
+# Copy any existing materials
+cp ~/Documents/relevant-files/* ~/Cowork-Workspace/input/meeting-[name]/
+```
+
+### Step 2: Define Meeting Context
+
+Tell Cowork about the meeting:
+
+```
+I have a meeting with [Company/Person] on [Date] at [Time].
+
+Meeting purpose: [describe]
+My role: [your position/company]
+Their role: [who you're meeting]
+What I want to achieve: [your goals]
+
+This context is for the briefing document you'll create.
+```
+
+### Step 3: Research Phase
+
+**Company Research:**
+```
+Research [Company Name] and create a company brief.
+
+Include:
+1. Company Overview
+   - What they do
+   - Size (employees, revenue if public)
+   - Founded, headquarters
+   - Key products/services
+
+2. Recent News
+   - Last 3-6 months
+   - Relevant announcements
+   - Press mentions
+
+3. Leadership
+   - CEO and key executives
+   - Board members (if relevant)
+
+4. Market Position
+   - Main competitors
+   - Market standing
+   - Recent changes
+
+Save to: ~/Cowork-Workspace/output/company-research.md
+```
+
+**Person Research:**
+```
+Research [Person Name] at [Company].
+
+Find:
+- Current title and responsibilities
+- Career background
+- Education (if available)
+- Public speaking/publications
+- LinkedIn summary points
+- Common topics they discuss
+- Any shared connections or interests
+
+Save to: ~/Cowork-Workspace/output/person-profile.md
+```
+
+### Step 4: Create Briefing Document
+
+```
+Create a meeting briefing document using:
+- Research you just compiled
+- Materials in ~/Cowork-Workspace/input/meeting-[name]/
+
+Structure:
+1. Meeting Overview
+   - Date, time, location/platform
+   - Attendees
+   - Purpose
+
+2. Company Background
+   - Key facts (from research)
+   - Relevant recent developments
+
+3. People Profiles
+   - Brief on each person I'm meeting
+
+4. Our History (if materials provided)
+   - Previous interactions
+   - Past discussions
+
+5. Talking Points
+   - 5-7 topics to cover
+   - Key messages to convey
+
+6. Questions to Ask
+   - 5-7 strategic questions
+   - Discovery questions
+   - Clarifying questions
+
+7. Potential Objections
+   - Likely concerns they might raise
+   - Suggested responses
+
+8. Meeting Goals
+   - What success looks like
+   - Minimum acceptable outcomes
+
+Format: Word document
+Save to: ~/Cowork-Workspace/output/meeting-brief.docx
+```
+
+### Step 5: Create Quick Reference Card
+
+```
+From the briefing document, create a 1-page quick reference card.
+
+Include only:
+- Key facts about company/person
+- Main talking points (bullets)
+- Critical questions
+- Names to remember
+
+Format: Can print and bring to meeting
+Save to: ~/Cowork-Workspace/output/quick-reference.docx
+```
+
+---
+
+## Meeting Type Variations
+
+### Sales/Client Meeting
+```
+Create a client meeting brief for [Company].
+
+Focus on:
+1. Their Business
+   - Industry, challenges, goals
+   - Decision-making process
+   - Budget cycle/timing
+
+2. Our Fit
+   - How our solution helps them
+   - Relevant case studies
+   - Competitive positioning
+
+3. Sales Strategy
+   - Entry points
+   - Value propositions
+   - Objection handling
+
+4. Next Steps
+   - Ideal meeting outcome
+   - Follow-up actions
+
+Save to: ~/Cowork-Workspace/output/client-brief.docx
+```
+
+### Job Interview
+```
+Create interview preparation document for [Company] [Role].
+
+Include:
+1. Company Research
+   - Culture and values
+   - Recent news
+   - Team structure (if known)
+
+2. Role Analysis
+   - Key responsibilities
+   - Required skills
+   - Success metrics (likely)
+
+3. My Fit
+   - Relevant experience points
+   - Stories to tell (STAR format)
+   - Skills to highlight
+
+4. Questions to Ask
+   - About the role
+   - About the team
+   - About growth
+
+5. Logistics
+   - Interview format
+   - Interviewer background
+
+Save to: ~/Cowork-Workspace/output/interview-prep.docx
+```
+
+### Partnership/Vendor Meeting
+```
+Create vendor evaluation brief for meeting with [Company].
+
+Include:
+1. Vendor Overview
+   - Company background
+   - Relevant products/services
+   - Market reputation
+
+2. Evaluation Criteria
+   - Must-have requirements
+   - Nice-to-have features
+   - Deal-breakers
+
+3. Questions Matrix
+   - Technical questions
+   - Pricing questions
+   - Support questions
+   - Contract questions
+
+4. Comparison Notes
+   - How they compare to alternatives
+   - Key differentiators
+
+Save to: ~/Cowork-Workspace/output/vendor-brief.docx
+```
+
+### Board/Executive Meeting
+```
+Create executive meeting brief for [meeting name].
+
+Include:
+1. Meeting Context
+   - Agenda items
+   - Key decisions needed
+   - Attendees and their interests
+
+2. Background Materials Summary
+   - Key points from supporting docs
+
+3. Recommendations
+   - What I'm proposing
+   - Supporting rationale
+   - Anticipated questions
+
+4. Stakeholder Map
+   - Who supports what
+   - Potential concerns by person
+   - Influence dynamics
+
+5. Presentation Notes
+   - Key messages
+   - Data points to cite
+   - Backup slides needed
+
+Save to: ~/Cowork-Workspace/output/executive-brief.docx
+```
+
+---
+
+## Troubleshooting
+
+### Can't find much about the company
+
+```
+Limited information available for [Company].
+
+For smaller/private companies, focus on:
+- What their website says
+- LinkedIn company page
+- Any news mentions
+- Industry context
+
+Note gaps in the briefing so I know what to research during the meeting.
+```
+
+### Research seems outdated
+
+```
+Verify this information is current (as of [today's date]).
+
+For any items more than 6 months old:
+- Note the date of the information
+- Flag if it might have changed
+- Suggest verification questions
+```
+
+### Person has common name
+
+```
+Research [Name] specifically at [Company] in [City/Role].
+
+Distinguish from others with same name.
+Use LinkedIn profile at: [URL if known]
+```
+
+---
+
+## Time-Saving Templates
+
+### Quick 15-Minute Prep
+```
+I have 15 minutes to prepare for a meeting with [Company/Person].
+
+Create a quick brief with:
+- 5 key facts about them
+- 3 talking points
+- 3 questions to ask
+- 1 paragraph company summary
+
+Save to: ~/Cowork-Workspace/output/quick-brief.md
+```
+
+### Recurring Meeting Update
+```
+Update the meeting brief at ~/Cowork-Workspace/input/previous-brief.docx
+
+Research any new developments since [last meeting date].
+Add to the existing document:
+- New news section
+- Updated talking points
+- New questions based on developments
+
+Save to: ~/Cowork-Workspace/output/updated-brief.docx
+```
+
+---
+
+## Best Practices
+
+1. **Start research early** — Web research takes time
+2. **Focus on relevance** — Not everything about a company matters
+3. **Prepare questions** — Shows engagement and drives conversation
+4. **Know your goals** — Clear objectives guide the brief
+5. **Update and reuse** — Briefs for recurring meetings can be updated
+
+---
+
+*[Back to Workflows](README.md) | [Cowork Documentation](../README.md)*
--- a/cowork/workflows/report-synthesis.md
+++ b/cowork/workflows/report-synthesis.md
@ -0,0 +1,350 @@
+# Workflow: Report Synthesis
+
+> **Estimated time**: 25 minutes
+> **Difficulty**: Intermediate
+
+---
+
+## Use Case
+
+You have multiple documents—meeting notes, emails, data files—and need to:
+
+- Combine information into a coherent report
+- Extract key points from various sources
+- Create structured deliverables
+- Summarize for different audiences
+
+---
+
+## Prerequisites
+
+- [ ] Cowork enabled in Claude Desktop
+- [ ] Source documents (text, PDF, Word, etc.)
+- [ ] Clear idea of the output format needed
+
+---
+
+## Step-by-Step Instructions
+
+### Step 1: Gather Source Documents
+
+```bash
+# Create workspace
+mkdir -p ~/Cowork-Workspace/{input/sources,output}
+
+# Copy all source documents
+cp ~/Documents/meeting-notes/*.txt ~/Cowork-Workspace/input/sources/
+cp ~/Documents/project-docs/*.pdf ~/Cowork-Workspace/input/sources/
+cp ~/Documents/data/*.xlsx ~/Cowork-Workspace/input/sources/
+```
+
+### Step 2: Document Inventory
+
+Have Cowork understand what's available:
+
+```
+List and summarize all documents in ~/Cowork-Workspace/input/sources/
+
+For each document, provide:
+- Filename
+- Type (meeting notes, report, data, etc.)
+- Date (if detectable)
+- Brief description (1-2 sentences)
+- Key topics covered
+
+Save inventory to ~/Cowork-Workspace/output/source-inventory.md
+```
+
+### Step 3: Define Report Structure
+
+Before asking for the report, define what you need:
+
+**Option A: Status Report**
+```
+Create a project status report from documents in ~/Cowork-Workspace/input/sources/
+
+Structure:
+1. Executive Summary (1 paragraph, 3-4 sentences)
+2. Progress This Period
+   - Completed items (bullet points)
+   - In progress items (bullet points)
+3. Key Metrics (extract any numbers/data)
+4. Decisions Made (list with date and context)
+5. Risks and Issues (prioritized list)
+6. Next Period Plans (bullet points)
+7. Action Items (table: Action, Owner, Due Date)
+
+Tone: Professional, concise
+Length: Maximum 4 pages
+Format: Word document
+Save to: ~/Cowork-Workspace/output/status-report.docx
+```
+
+**Option B: Meeting Summary**
+```
+Create a consolidated meeting summary from notes in ~/Cowork-Workspace/input/sources/
+
+Structure:
+1. Meeting Overview
+   - Dates covered
+   - Participants mentioned
+   - Topics discussed
+
+2. Key Discussions
+   - Topic 1: [summary]
+   - Topic 2: [summary]
+   - ...
+
+3. Decisions Log
+   - Date | Decision | Context | Owner
+
+4. Action Items
+   - All action items from all meetings
+   - Deduplicated
+   - Sorted by due date
+
+5. Open Questions
+   - Questions raised but not resolved
+
+Format: Word document
+Save to: ~/Cowork-Workspace/output/meeting-summary.docx
+```
+
+**Option C: Executive Brief**
+```
+Create an executive brief from all documents in ~/Cowork-Workspace/input/sources/
+
+Requirements:
+- ONE PAGE MAXIMUM
+- Focus on: What happened, Why it matters, What's next
+- Include only critical numbers
+- Bullet points preferred
+- Clear recommendations at the end
+
+Format: Word document
+Save to: ~/Cowork-Workspace/output/executive-brief.docx
+```
+
+### Step 4: Review and Refine
+
+After initial generation, refine as needed:
+
+```
+Review the report you created. Make these adjustments:
+- Expand the section on [topic]
+- Add more detail about [specific item]
+- Move [section] before [other section]
+- Add a table summarizing [data]
+```
+
+### Step 5: Create Alternate Versions (Optional)
+
+For different audiences:
+
+```
+Create a simplified version of the status report for non-technical stakeholders.
+
+Changes:
+- Remove technical jargon
+- Focus on outcomes, not process
+- Add more context for acronyms
+- Shorten to 2 pages maximum
+
+Save to: ~/Cowork-Workspace/output/status-report-stakeholder.docx
+```
+
+---
+
+## Example Report Types
+
+### Weekly Team Update
+```
+Create weekly team update from:
+- ~/Cowork-Workspace/input/sources/ (this week's notes)
+
+Include:
+- Wins (what went well)
+- Progress (what moved forward)
+- Blockers (what's stuck)
+- Learnings (what we discovered)
+- Next week focus
+
+Format: Markdown (for Slack/email)
+Tone: Conversational but professional
+Save to: ~/Cowork-Workspace/output/weekly-update.md
+```
+
+### Quarterly Review
+```
+Create Q[X] review document from quarterly materials in ~/Cowork-Workspace/input/sources/
+
+Structure:
+1. Quarter Highlights (3-5 bullets)
+2. Goals vs. Actuals (table format)
+3. Key Achievements
+4. Challenges Faced
+5. Lessons Learned
+6. Q[X+1] Priorities
+7. Resource Needs
+
+Include charts/tables where data supports
+Save to: ~/Cowork-Workspace/output/quarterly-review.docx
+```
+
+### Research Summary
+```
+Synthesize research documents in ~/Cowork-Workspace/input/sources/
+
+Create research summary with:
+1. Research Questions Addressed
+2. Methodology Overview
+3. Key Findings
+   - Finding 1 (with supporting evidence)
+   - Finding 2 (with supporting evidence)
+   - ...
+4. Implications
+5. Recommendations
+6. Limitations
+7. Next Steps
+
+Save to: ~/Cowork-Workspace/output/research-summary.docx
+```
+
+---
+
+## Troubleshooting
+
+### "Context limit" errors
+
+**Cause**: Too many documents for one session
+
+**Solution**: Process in chunks
+```
+Start with just these files:
+- file1.txt
+- file2.txt
+- file3.txt
+
+Create partial summary. I'll provide more files in next message.
+```
+
+### Important information missing
+
+```
+The report is missing information about [topic].
+
+Check these specific files for that information:
+- [filename1]
+- [filename2]
+
+Add a section covering [topic] with details from those files.
+```
+
+### Conflicting information in sources
+
+```
+I notice conflicting information in the sources about [topic]:
+- Document A says X
+- Document B says Y
+
+In the report:
+1. Note the discrepancy
+2. Use the most recent information
+3. Flag for verification
+```
+
+### Report is too long
+
+```
+Condense the report to [X] pages.
+
+Prioritize:
+1. Executive summary
+2. Key decisions
+3. Action items
+
+Move detailed information to an appendix section.
+```
+
+### Report is too short/vague
+
+```
+Expand the report with more detail:
+
+Specifically:
+- Add specific examples for each finding
+- Include relevant quotes from source documents
+- Add data points where available
+- Elaborate on recommendations
+```
+
+---
+
+## Variations
+
+### Multi-Audience Reports
+
+Create one source report, then variants:
+
+```
+# Step 1: Comprehensive report
+Create detailed report... [full prompt]
+
+# Step 2: Executive version
+From the report you just created, make an executive summary:
+- 1 page maximum
+- Key points only
+- Clear recommendations
+Save to ~/Cowork-Workspace/output/report-executive.docx
+
+# Step 3: Team version
+From the report you created, make a team version:
+- Focus on action items and next steps
+- Include more tactical detail
+- Remove strategic context
+Save to ~/Cowork-Workspace/output/report-team.docx
+```
+
+### Incremental Updates
+
+For ongoing projects:
+
+```
+I have a previous report at ~/Cowork-Workspace/input/previous-report.docx
+New documents are in ~/Cowork-Workspace/input/sources/
+
+Create an updated report that:
+- Builds on the previous report
+- Adds new information from recent documents
+- Moves completed items to "Completed" section
+- Updates status of ongoing items
+
+Save to ~/Cowork-Workspace/output/updated-report.docx
+```
+
+### With Data Visualization
+
+```
+Create the status report AND prepare visualization data:
+
+Main report: ~/Cowork-Workspace/output/status-report.docx
+
+Supporting data: ~/Cowork-Workspace/output/charts-data.xlsx
+- Sheet 1: Progress over time (for line chart)
+- Sheet 2: Tasks by status (for pie chart)
+- Sheet 3: Team allocation (for bar chart)
+```
+
+---
+
+## Best Practices
+
+1. **Define structure first** — Know what output you need before starting
+2. **Quality in, quality out** — Well-organized sources yield better reports
+3. **Iterate** — First draft rarely perfect; refine in follow-up prompts
+4. **Verify facts** — Spot-check key numbers and claims
+5. **Keep sources** — Don't delete until report is final
+
+---
+
+*[Back to Workflows](README.md) | [Cowork Documentation](../README.md)*
--- a/cowork/workflows/team-handoff.md
+++ b/cowork/workflows/team-handoff.md
@ -0,0 +1,408 @@
+# Workflow: Team Handoff (Dev ↔ Non-Dev)
+
+> **Estimated time**: 30 minutes
+> **Difficulty**: Advanced
+
+---
+
+## Use Case
+
+Your team has both technical (developers using Claude Code) and non-technical members (PMs, analysts using Cowork). This workflow enables:
+
+- Seamless handoff between Claude Code and Cowork
+- Shared context and documentation
+- Complementary capabilities
+- Efficient collaboration
+
+---
+
+## Prerequisites
+
+- [ ] Shared folder accessible to both team members
+- [ ] Claude Code for developer
+- [ ] Cowork for non-technical member
+- [ ] Agreed conventions (folder structure, naming)
+
+---
+
+## Setting Up Shared Infrastructure
+
+### Step 1: Create Shared Workspace
+
+```bash
+# On developer's machine (or shared drive)
+mkdir -p ~/Shared/{specs,docs,research,data,handoff}
+```
+
+### Step 2: Create Shared CLAUDE.md
+
+Both Claude Code and Cowork can reference this context file:
+
+```markdown
+# ~/Shared/CLAUDE.md
+
+## Project: [Project Name]
+
+### Folder Conventions
+- `/specs/` - Technical specifications (from dev)
+- `/docs/` - Business documents (from PM/analyst)
+- `/research/` - Research materials (either)
+- `/data/` - Data files for analysis
+- `/handoff/` - Active handoff items
+
+### Active Items
+- [List current work items]
+
+### Team
+- Dev: [Name] - Uses Claude Code
+- PM: [Name] - Uses Cowork
+- Analyst: [Name] - Uses Cowork
+
+### Current Sprint
+- [Sprint goals]
+
+### Key Decisions
+- [Important decisions with dates]
+```
+
+---
+
+## Pattern 1: Developer → PM Handoff
+
+**Scenario**: Developer creates technical spec, PM needs stakeholder summary.
+
+### Developer (Claude Code)
+
+```bash
+# Developer creates technical specification
+claude "Create a technical specification for the authentication system.
+Include: architecture diagram (text), API endpoints, data models,
+security considerations, and implementation phases.
+Save to ~/Shared/specs/auth-spec.md"
+```
+
+### PM (Cowork)
+
+```
+Read the technical spec at ~/Shared/specs/auth-spec.md
+
+Create a stakeholder summary document that:
+1. Explains the feature in non-technical terms
+2. Highlights business benefits
+3. Identifies timeline and phases
+4. Lists resource needs
+5. Flags any risks or dependencies
+
+Format: Word document for presentation
+Save to: ~/Shared/docs/auth-stakeholder-summary.docx
+```
+
+### Handoff File
+
+Create a handoff note:
+
+```
+Create a handoff note at ~/Shared/handoff/auth-handoff.md
+
+Include:
+- Source: ~/Shared/specs/auth-spec.md
+- Created by: [Dev name]
+- Date: [today]
+- Destination: ~/Shared/docs/auth-stakeholder-summary.docx
+- Created by: [PM name]
+- Status: Ready for stakeholder review
+- Next steps: [what happens next]
+```
+
+---
+
+## Pattern 2: Research → Implementation
+
+**Scenario**: Analyst does competitive research, developer implements based on findings.
+
+### Analyst (Cowork)
+
+```
+Research competitors' pricing pages for our industry.
+
+For each competitor:
+- Screenshot (via Chrome)
+- Pricing tiers and features
+- UX patterns observed
+- What works well / what doesn't
+
+Create:
+1. ~/Shared/research/pricing-comparison.xlsx (detailed matrix)
+2. ~/Shared/research/pricing-analysis.md (summary and recommendations)
+3. ~/Shared/research/screenshots/ (reference images)
+```
+
+### Developer (Claude Code)
+
+```bash
+# Developer reads research and implements
+claude "Review the competitive research at ~/Shared/research/
+
+Based on the analysis:
+1. Create a pricing page component that incorporates best practices identified
+2. Follow the recommended tier structure from pricing-analysis.md
+3. Use our existing design system
+
+Implementation should be in src/pages/pricing/"
+```
+
+---
+
+## Pattern 3: Data Analyst → Developer
+
+**Scenario**: Analyst identifies data patterns, developer needs to build features.
+
+### Analyst (Cowork)
+
+```
+Analyze the user data in ~/Shared/data/user-metrics.csv
+
+Create analysis report:
+1. Key user behavior patterns
+2. Most common user journeys
+3. Drop-off points
+4. Feature usage statistics
+5. Recommendations for product improvements
+
+Save to: ~/Shared/docs/user-analysis.docx
+Include: charts-data.xlsx for any visualizations
+```
+
+### Developer (Claude Code)
+
+```bash
+# Developer builds features based on analysis
+claude "Review the user analysis at ~/Shared/docs/user-analysis.docx
+
+Based on the drop-off points identified:
+1. Implement improvements to reduce friction
+2. Add analytics tracking for recommended metrics
+3. Create A/B test framework for suggested changes
+
+Start with the highest-impact recommendation."
+```
+
+---
+
+## Pattern 4: Bidirectional Collaboration
+
+**Scenario**: Ongoing collaboration on a document/feature.
+
+### Shared Document Workflow
+
+**PM starts:**
+```
+Create a PRD (Product Requirements Document) for the new dashboard feature.
+
+Structure:
+1. Problem Statement
+2. User Stories
+3. Requirements (functional)
+4. Success Metrics
+5. [Technical Requirements - TO BE FILLED BY DEV]
+6. Timeline
+7. Open Questions
+
+Save to: ~/Shared/docs/dashboard-prd.docx
+```
+
+**Developer adds:**
+```bash
+claude "Read the PRD at ~/Shared/docs/dashboard-prd.docx
+
+Add a Technical Requirements section:
+- Architecture approach
+- API endpoints needed
+- Data models
+- Performance requirements
+- Technical risks
+
+Save updated version to same location."
+```
+
+**PM finalizes:**
+```
+Review the updated PRD at ~/Shared/docs/dashboard-prd.docx
+
+Add:
+- Timeline based on technical requirements
+- Resource allocation
+- Final open questions
+
+Create final version: ~/Shared/docs/dashboard-prd-final.docx
+```
+
+---
+
+## Handoff Protocols
+
+### Standard Handoff Template
+
+```markdown
+# Handoff: [Item Name]
+
+## Source
+- **File**: [path to source file]
+- **Created by**: [name]
+- **Date**: [date]
+- **Tool used**: [Claude Code / Cowork]
+
+## Destination
+- **Expected output**: [what should be created]
+- **Owner**: [who will process this]
+- **Due**: [deadline if any]
+
+## Context
+[Any important context for the recipient]
+
+## Instructions
+[Specific instructions for processing]
+
+## Dependencies
+- [Any files or information needed]
+
+## Completion Criteria
+- [ ] [Criterion 1]
+- [ ] [Criterion 2]
+```
+
+### Notification System
+
+Create a simple notification file:
+
+```
+# ~/Shared/handoff/INBOX.md
+
+## Pending Items
+
+### [Date] - [Item Name]
+- From: [sender]
+- To: [recipient]
+- Priority: [High/Medium/Low]
+- Handoff file: [link]
+- Status: [ ] Pending / [x] Received / [ ] Complete
+```
+
+---
+
+## Best Practices
+
+### 1. Consistent Naming
+```
+Agree on naming conventions:
+- specs/[feature]-spec.md
+- docs/[feature]-summary.docx
+- research/[topic]-analysis.md
+- handoff/[date]-[item]-handoff.md
+```
+
+### 2. Clear Ownership
+Each file should indicate:
+- Who created it
+- Who should process it
+- Current status
+
+### 3. Version Tracking
+```
+Use date prefixes for versions:
+- 2024-01-15-dashboard-prd-v1.docx
+- 2024-01-20-dashboard-prd-v2.docx
+```
+
+### 4. Status Updates
+Update the shared CLAUDE.md with current status:
+```markdown
+### Active Handoffs
+| Item | From | To | Status | Due |
+|------|------|-----|--------|-----|
+| Auth spec | Dev | PM | In review | Jan 20 |
+```
+
+### 5. Feedback Loop
+After each handoff:
+```
+Create feedback note at ~/Shared/handoff/feedback/[item]-feedback.md
+
+Include:
+- What worked well
+- What was missing
+- Suggestions for next time
+```
+
+---
+
+## Troubleshooting
+
+### Cowork can't read Claude Code output
+
+**Issue**: Format incompatibility or location mismatch
+
+**Solution**:
+- Ensure files are in shared location
+- Use standard formats (.md, .docx, .xlsx)
+- Avoid code-specific formats
+
+### Context lost between tools
+
+**Issue**: Each tool starts fresh
+
+**Solution**:
+- Use CLAUDE.md for persistent context
+- Include relevant background in each prompt
+- Reference source files explicitly
+
+### Conflicting edits
+
+**Issue**: Both tools editing same file
+
+**Solution**:
+- Use clear ownership per file
+- Create new versions instead of editing
+- Lock files during active work
+
+---
+
+## Example: Complete Feature Cycle
+
+### Phase 1: Research (Cowork)
+```
+Research notification best practices.
+Save to ~/Shared/research/notifications-research.md
+```
+
+### Phase 2: Spec (Claude Code)
+```bash
+claude "Based on research at ~/Shared/research/notifications-research.md,
+create technical spec at ~/Shared/specs/notifications-spec.md"
+```
+
+### Phase 3: Documentation (Cowork)
+```
+Create user-facing documentation based on
+~/Shared/specs/notifications-spec.md
+Save to ~/Shared/docs/notifications-user-guide.docx
+```
+
+### Phase 4: Implementation (Claude Code)
+```bash
+claude "Implement notifications feature per
+~/Shared/specs/notifications-spec.md"
+```
+
+### Phase 5: Release Notes (Cowork)
+```
+Create release notes for stakeholders based on:
+- ~/Shared/specs/notifications-spec.md
+- ~/Shared/docs/notifications-user-guide.docx
+
+Save to ~/Shared/docs/notifications-release.docx
+```
+
+---
+
+*[Back to Workflows](README.md) | [Cowork Documentation](../README.md)*