Skip to main content

Teacher’s Edition

Module 08

Writing with Claude

Claude as Generator and Claude as Editor. Two different roles, two different skill sets. The Editor role is where "it sounds like AI" stops being a problem: your voice goes in, a cleaner version comes out.

70 minutesAll rolesPrerequisite: Module 05

Charter Oak Strategic Partners · Claude Mastery Program · Version 1.0 · Confidential · Not for distribution to participants

Back to Module|Teacher’s Guide
Concept: Generator vs. Editor

Claude plays two writing roles. Generator: it creates from scratch based on your prompt. Editor: it improves existing work you give it. Most people use only the Generator role. The Editor role is often more valuable because it starts from your ideas and your voice, then improves the execution. The distinction matters because the prompts are different. A Generator prompt says “write a memo about X.” An Editor prompt says “here is my draft memo. The opening buries the point. The third paragraph uses jargon my audience will not understand. Rewrite the opening to lead with the recommendation, and simplify the jargon without losing the technical accuracy.”

The revision loop technique combines both roles. You generate a draft, ask Claude to critique its own work (identifying the three weakest sentences and explaining why), then ask it to revise based on the critique. This separation of generation and evaluation produces better results than trying to get a perfect draft in a single pass.

Opening — 5 minutes

Script: Two Roles

“Claude plays two roles when you write with it. Generator: create from nothing. Editor: improve what exists. Most people only use the first. The second is often better because it starts with your ideas and your voice.”

“The complaint I hear most often about Claude’s writing is ‘it sounds like AI.’ That complaint disappears when you use Claude as an editor instead of a generator. Your voice goes in. A cleaner version of your voice comes out.”

Live Demo: Three Bad Pieces — 25 minutes

demo-data/module-08/writing-samples-before-after.mdThree samples with problems, rewrite prompts, teaching notes.
Concept: The Three Samples

Sample 1: The Overwritten Memo. A team update stuffed with corporate jargon: “leveraging cross-functional synergies,” “robust pipeline of deliverables,” “driving alignment across stakeholders.” The specific problem: every sentence contains at least one word that means nothing. The rewrite prompt tells Claude to strip the jargon, lead with the actual update, and limit the memo to 200 words. The teaching point: Claude can identify and remove jargon when told to, but the prompt must name what jargon looks like.

Sample 2: The Buried Lede Email. A price increase notification that buries the price change in paragraph four after three paragraphs of context about market conditions and cost pressures. The specific problem: the reader has to dig for the information that matters. The rewrite prompt says: “The price increase is the news. Put it in the first sentence. The context is the justification. Put it after.” The teaching point: Claude follows structural instructions precisely when they are clear.

Sample 3: The Jargon-Loaded Report. A quarterly performance report using phrases like “robust momentum,” “secular tailwinds,” “optimize our go-to-market motion.” The specific problem: the report sounds impressive and communicates nothing. The rewrite prompt tells Claude to replace every abstract phrase with a concrete fact or number. “Robust momentum” becomes “revenue grew 12% QoQ.” The teaching point: the rewrite prompt must define what “good” looks like. “Make it clearer” is insufficient. “Replace every abstract phrase with a specific number or fact” is actionable.

Script: Running the Demo

For each sample, follow this pattern:

Show the bad original on screen. Read the worst sentence aloud. Name the specific problem: “This memo has six words that mean nothing. Leveraging. Synergies. Robust. Pipeline. Deliverables. Alignment. These words fill space. They do not inform.”

Then paste the rewrite prompt. Show the output.

“Notice what the prompt did not say. It did not say ‘make it better.’ It said exactly what was wrong and exactly what right looks like. That is the difference between a vague request and an editing instruction.”

Ask the Room: After Each Sample

“What made the rewrite prompt effective? What specific instruction drove the biggest improvement?”

Technique: The Revision Loop — 10 minutes

Script: Teaching the Loop

“Here is a five-step workflow that produces better writing than any single prompt.”

“Step 1: Give Claude your rough outline or bullet points. Just the ideas. Messy is fine.”

“Step 2: Ask Claude to draft it. Specify voice and constraints.”

“Step 3: Read the draft. Then ask Claude: ‘What are the three weakest sentences in this draft, and why?’ Claude critiques its own work. It is surprisingly good at this.”

“Step 4: Tell Claude to revise based on its own critique.”

“Step 5: Final polish. Specific instructions. ‘Tighten the opening paragraph. Make the call-to-action more specific. Remove the second example, it is weaker than the other two.’”

“Why does this work? Because it separates generation from evaluation. Claude is good at both. It is less good at both simultaneously.”

Individual Exercise — 20 minutes

Script: Launching the Exercise

“Bring a piece of your own writing. An email you sent this week. A report section. A project update. If you do not have one, write one from memory.”

“Choose your role. Generator: start from scratch with a structured prompt. Editor: paste your existing draft and ask Claude to improve it using the revision loop.”

“Document the before and after. We will share.”

Debrief — 10 minutes

Ask the Room: Generator vs. Editor Results

“Who used Claude as a Generator? Who used it as an Editor? Which group is more satisfied with the result?”

The pattern: editors are almost always more satisfied. Their output preserved their ideas while improving the execution. Generators often feel the output sounds generic because Claude had no starting material to work from. This is the lesson: when you have something to say, use Claude as an editor. When you have nothing to say, use Claude as a generator. Knowing which mode to choose is the skill.

SegmentActivityTime
OpeningGenerator vs. Editor roles5 min
DemoThree bad pieces rewritten25 min
TechniqueThe Revision Loop10 min
ExerciseIndividual writing improvement20 min
DebriefBefore/after sharing10 min