Write For Audience — Development skill for Claude Code

write-for-audience

A Claude Code skill. Two questions before writing anything a human reads, so the words land with the person who has to act on them.

Problem

You write something true and nothing happens.

The complaint is real. The proposal is sound. The doc is accurate. But it is pitched at nobody in particular, so the person who could act on it asks you to start over or scrolls past.

See this exchange on X:

Solution

Two questions, every time:

1. Who is the audience? If the request does not say, ask. Do not guess.
2. What role does that audience need? Marketer, instructor, consultant, engineer.

`SKILL.md` is 23 lines: the two questions and a routing table. Each role's rules live in `references/` and load only when that role is chosen, so a session that needs the engineer voice never reads the marketer's rules.

Examples

Below are lines from two real sweeps, both against copy Claude had already written and shipped.

Marketer

Audience: buyers scanning a B2B website, gone in seconds. Sweep: 30 lines across 14 pages.

Before	After
"Reading is a start. A conversation is faster."	"Talk to us about your process"
"If one document process is eating your team's week, bring it to a discovery call."	"Book a discovery call and walk us through your document process."
"on the tier already priced above: in production, not a pilot."	"Pick a tier above, bring one real process, and see it running in production."
"Start with one process, not a risky transformation programme"	"Start with one process, expand when it works"