Build a useful writing voice guide

A voice guide should describe observable choices a reviewer can apply. Use examples and boundaries instead of broad adjectives alone.

Set the editorial constraints

Give the writing teammate a clear audience, purpose and approved facts. Include a short voice sample when tone matters, and state what the draft must not promise. Save a draft file for review rather than treating a generated message as published copy. A final human edit should verify names, dates, claims and links against the source material.

Inputs for this workflow: Approved writing samples and examples the team dislikes.

Work through the task

1. Extract recurring sentence and vocabulary choices.
2. Pair each rule with a before-and-after example.

A brief you can adapt

Create voice-guide.md with audience, tone rules, preferred terms, prohibited claims and annotated examples from the supplied material.

The filenames above are examples. Replace them with your actual inputs and destination before submitting the task.

Review the deliverable

Have two reviewers edit a short draft with the guide and compare where the rules led to different choices.

Where this approach can fail

One sample does not establish a universal brand rule. Mark tentative patterns for confirmation.

For the related desktop setup, see company playbook.