Purposeful Writing

---
name: purposeful-writing
description: "Use when drafting or revising prose for a reader: application answers, emails, essays, bios, cover letters, proposals, memos, reports, product copy, speeches, or when a draft reads as machine-made or must match a writer's own voice."
---

# Purposeful Writing

## Overview

Write for the reader's next decision.

Every piece of writing has a job: answer a question, earn trust, explain a choice, request action, record a decision. Find that job, do it early, and remove everything that does not help.

Do not write to sound impressive. Write to make the reader understand, believe, or act.

## When to Use

Any drafting or revision task: application answers, emails, essays, bios, cover letters, proposals, memos, reports, product copy, messages, speeches, long-form prose. Also for de-slopping a machine-sounding draft or matching a writer's voice.

The draft, prompt, constraints, and any voice sample come from the user's message or the files it names.

Use a specialized skill instead when the task has domain rules: research, legal writing, technical documentation, book chapters.

## Before Writing

Identify, silently (do not narrate this planning):

1. **Reader:** Who will read this?
2. **Purpose:** What should they understand, feel, decide, or do?
3. **Prompt:** What is the question actually asking? A question about a challenge may really ask for judgment, resilience, or fit. Answer that, not the chronology.
4. **Constraints:** Length, format, tone, required details.
5. **Best material:** Which facts, examples, or reasons carry the answer?

If the writer provides a sample of their own writing, read it first and mirror its rhythm, word choice, and punctuation habits. Do not upgrade a casual voice into corporate prose.

**Precedence:** the writer's demonstrated voice overrides the style rules below, including the AI-tell list. Keep their semicolons, long sentences, and distinctive phrasing. The one exception is em dashes: never use them, even if the sample does. Replace with commas, periods, or parentheses.

## Core Rules

### Answer early

Lead with the answer, point, request, or most useful fact. No background, disclaimers, or scene-setting first unless the task truly needs them.

### Be specific

Concrete details beat claims about yourself or the subject.

Weak:
> I am a strong leader who works well with others.

Better:
> I ran the weekly handoff between design and engineering, which cut the average review cycle from five days to two.

Never invent details, outcomes, credentials, or numbers. Invented specificity is worse than vague prose. If the material is thin, write plainly from what is known.

### Match the form to the job

- **Application answer:** Answer the prompt, one relevant example, what it reveals.
- **Email:** Purpose first, essential context, obvious next step.
- **Explanation:** Answer, then how or why.
- **Proposal:** Problem, recommendation, why it is worth doing.
- **Memo:** Decision or finding, then implications and action.
- **Bio:** Most relevant identity or work first, then evidence.
- **Essay:** A claim worth following, then earn it.
- **Product copy:** The user's task or outcome, not the product's self-description.

### Use plain, active language

Concrete nouns, strong verbs, short words, active voice. Say "I led the project," not "I was responsible for leading the project."

### Cut AI tells

Certain words and shapes mark writing as machine-made. Scan for them, then cut or rewrite:

- **Inflated vocabulary:** delve, crucial, pivotal, testament, showcase, foster, leverage, utilize, robust, seamless, vibrant, tapestry, underscore, landscape (abstract). Use the plain word.
- **Copula dodges:** "serves as," "stands as," "boasts." Say "is" or "has."
- **Fake structure:** rule-of-three lists ("innovation, inspiration, and insight"), "not just X, it's Y," and "from X to Y" ranges where X and Y are not a real scale.
- **Filler openers and closers:** "Great question," "Let's dive in," "It's important to note," "I hope this helps," "In today's world."
- **Formula sections:** "Despite these challenges, X continues to thrive," "The future looks bright."
- **Style tics:** em dashes, colons used as mid-sentence connectors, boldface on every noun, inline-header bullets that restate their own label, Title Case headings, decorative emojis.
- **Vague attribution:** "experts say," "studies show," "it is widely regarded." Name the source or cut the claim.
- **Feeling over mechanism:** "stays close at hand," "unlocks seamless experiences." Say what it does, returns, or costs.

The full catalog with before/after examples lives in the `$humanizer` skill's [`patterns.md`](../humanizer/patterns.md). Read it when a tell is ambiguous. Do not trade one tell for another: swapping em dashes for semicolon piles is the same problem in new clothes.

### Preserve voice

Sound like a thoughtful person, not a template.

- Keep distinctive phrasing, earned confidence, dry humor, intentional roughness.
- Have a view. React to the facts; do not only list neutral pros and cons.
- Vary rhythm. Short sentences. Then a longer one with room to turn.
- Let some asymmetry in; perfect parallel structure feels generated.
- First person is not unprofessional.

Fix accidental awkwardness. Do not smooth writing into bland professional language.

### Earn every claim

Never say passionate, innovative, hard-working, strategic, or collaborative unless the surrounding sentence shows what that looks like. Demonstration beats self-description.

### Respect constraints

Meet word limits, formats, and required questions exactly. A short response gets no long introduction. Formal is not stiff; personal is not confessional unless the prompt calls for it.

## Revision Pass

Before delivering:

1. **Prompt:** Did this answer the actual question, including its hidden demand?
2. **Order:** Does the strongest material arrive early? Does it end on the decision, result, or request, not a trailing summary?
3. **Specificity:** Are claims backed by concrete, real detail?
4. **Voice:** Does it sound like the writer, not a template? Anything still reading as a bot, fix it, then stop.
5. **Economy:** Can any sentence be cut without loss?
6. **Constraints:** Requested length, format, tone, met exactly?

Never use em dashes.

## Source

Adapted from `purposeful-writing` 1.2.1 by Hermes Agent, MIT license, as recorded in `.claude/skills/purposeful-writing/SKILL.md`.