Private course for your team

Document Generation in Claude Cowork

Stop pushing that document to next week. Generate it, prove it is right, and make it repeatable.

Length

1 day

Format

Virtual or on-site

Structure

6 hands-on labs

Level

No coding required

Request information

The problem

You have the material already: a feature list in Excel, a user guide one release out of date, a template someone insists on. Hand the folder to Claude and what comes back looks finished, reads well, and is wrong in about eight specific places. Every one of those errors was already sitting in your source files; the draft just repeated them with more confidence than they deserved.

What your team walks away with

  • A finished, formatted Word document built from real spreadsheets and prior versions.
  • A five-item rubric that says whether a draft is good enough to send.
  • An evidence line behind every score, so the judgment can be defended.
  • Automatic checks for missing sections, figures and scope errors.
  • The habit of fixing the inputs rather than rewriting the prompt.
  • A scored before and after, so the improvement is a number rather than an opinion.
  • A reusable skill, so the next document takes minutes.

The labs

1

The baseline

Generate a first chapter from the supplied files, then read it properly instead of skimming it, and see what a confident wrong draft looks like.

2

Turn the failures into a rubric

Five items, twenty points each, and a stated reason for a zero.

3

Check it automatically

Rules for what can be counted, eyes for what cannot, and the evidence line behind every score.

4

Fix the inputs, not the prompt

Clean the source material, generate again, and see whether the number actually moved.

5

Make it repeatable

Package the procedure as a skill and point it at next month’s release instead of starting over.

6

Scale with agents

Several writers, one reviewer, one finished document, and a clear view of when that is worth it.

Who it's for

  • Business analysts, technical writers and product teams.
  • Consultants and operations staff who own recurring reports.
  • Anyone on Claude Team or Enterprise who writes the same kind of document repeatedly.

What you need

  • Claude Desktop on a Claude Team or Enterprise plan, with Cowork enabled.
  • A setup guide and check script go out a week before.

Taught by James Harmon

Independent consultant and trainer based in the Chicago area, specializing in the Anthropic Claude ecosystem. Author of Design Patterns for AI Agents. Over 20 years building software for companies including JPMorgan Chase, State Farm and Foot Locker. Runs XoSelf.

XoSelf also takes on a small number of Claude consulting engagements: rollout, agents and MCP integrations. Mention it in your request.

About the book

Request information

Tell us a little about your team and James will come back with dates, pricing and what the day would look like for you.

No newsletter, no sales sequence. James reads these himself.