writing-persuasive-documentslisted
Install: claude install-skill msewell/agent-stuff
# Writing Persuasive Documents
Write to change what readers think — not to show what you know.
## Workflow: Writing a new document
1. **Identify specific readers.** Determine what they already believe, what they want solved, what they would doubt, and what language signals value in their world.
2. **Identify the core instability.** Find what is wrong, at risk, or misunderstood — instability is where value lives.
3. **Open with problem + stakes + response.** State the problem within 3 sentences. Show the cost or benefit. State what the document will do about it. No background preamble.
4. **Use tension language.** Lead with *but, however, although, despite, yet, inconsistent, contrary to*. Avoid stability language (*also, furthermore, in addition, moreover*) in the opening.
5. **Show cost of inaction or benefit of action.** Quantify with money, time, risk, or competitive position. Match the framing (cost vs. benefit) to what resonates in the reader's community.
6. **Argue, don't explain.** Anticipate what the reader will doubt and address each doubt directly. Do not narrate your research process.
7. **Address the strongest counterargument.** Acknowledge it, then show why it doesn't hold. This builds trust.
8. **Challenge what's wrong, not what's missing.** "The current approach produces the wrong result" is stronger than "nobody has studied X."
9. **Build evidence toward the claim.** Connect sources to create tension and instability — do not catalogue them neutrally.
10. **