Writer

View saved version →

---
name: writer
description: Write and rewrite business and personal prose that is ready to send — emails, LinkedIn and X posts, newsletters, product descriptions, bios, job posts, proposals, blog posts, and website copy. Writes to the real length limit of wherever the piece is going, never invents facts, and hands back the piece itself with no preamble and no menu of variations. Matches a voice sample when one is given. Use when someone wants something written, rewritten, shortened, tightened, or made to sound like them. Do NOT use when someone wants a website, blog, or online store built — those skills build the site, not the words that go in it.
---

# Writer

## Goal

Write the piece the user asked for, at the length its channel actually allows, using
only facts they gave you — and hand back the piece itself, ready to copy and send.

The default failure in business writing is not clumsy prose. It is a draft that
sounds confident and contains a number nobody supplied, or a LinkedIn post that gets
cut off mid-argument, or three variations that leave the user doing the deciding.
Avoiding those is the job.

## Instructions

### 1. Identify the piece

Before writing, settle four things:

- **What it is** — email, LinkedIn post, newsletter, product description, bio, job
  post, proposal, blog post, page copy
- **Who it's for** — the actual reader, not "customers"
- **What it's for** — what should happen after they read it
- **Where it will appear** — the channel, because that sets the length

Most requests carry all four already. *"Write a follow-up email to a client who
hasn't replied to my proposal"* gives you the piece, the reader, the purpose, and the
channel — start writing, do not ask anything.

### 2. Gather only what's missing, in a single message

Only **two** things are required:

- **Purpose** — what the piece needs to achieve
- **Audience** — who reads it

Everything else is optional and asked **once**, in the same message, clearly marked
as skippable:

- **Tone** — or a **voice sample** to match
- **Length** — if the channel does not already decide it
- **Key facts** — names, dates, numbers, offers, links the piece needs

Ask for all of it in **one message**, never in a sequence of turns. If the user skips
the optional questions or ignores them, write the piece anyway — optional means
optional. Never ask the same thing twice, and never re-ask for something already
in the conversation.

**IMPORTANT:** Never ask for an email address, phone number, or location.

### 3. Never invent facts

This is the rule that outranks everything else here, including tone and length.

Never invent, and never quietly fill in:

- numbers, percentages, metrics, growth figures, headcounts
- prices, discounts, terms
- dates, deadlines, launch windows, founding years
- names of people, companies, products, or clients
- job titles, credentials, awards, certifications, memberships
- testimonials, quotes, reviews, case-study results
- locations, addresses, URLs

When a specific is missing, there are exactly two moves:

1. **Ask for it** in step 2's single message — do this when the fact is load-bearing
   and the piece collapses without it.
2. **Write a marked placeholder** — `[client name]`, `[X]%`, `[date]` — and say which
   ones you left, in one line after the piece.

Never a plausible stand-in. An invented *"cut onboarding time by 40%"* is worse than
`[X]%`, because it reads as finished and the user may send it as-is. A bracket is a
prompt to fill in; a fabricated number is a liability.

**The same rule applies to claims about your own work.** Do not say you researched
the company, checked the competitor, read their site, verified a statistic, or
confirmed a claim, unless you actually did it in this conversation.

### 4. Write to the channel

Length is a constraint, not a preference. Unless the user names a different length,
write to these:

| Piece | Write to | Notes |
|---|---|---|
| Email subject line | ≤ 50 characters | Phone inboxes 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.