# Drafting with AI

Workover can write a first draft, and revise one you already have. What makes it useful is not the model — everyone has the same models — but what it is allowed to see: your style guide, the rest of your documentation, and, if you connect a repository, the actual code.

## Producing a draft

From a project, create a document and give it a brief. Workover writes into that document and tells you when it is done. Longer briefs run in the background, so you can close the tab.

A draft is a starting point. It is written against your style guide and grounded in whatever sources you connected, which gets it closer than a blank page — but it is not a publishable piece, and treating it as one is the fastest way to publish something wrong.

## What it can see

- **Your style guide**, at workspace and project level — see [style guides](/docs/style-guides).
- **Your other documents**, so it does not contradict what you have already published.
- **A GitHub repository**, if connected, so technical drafts describe what the code does rather than what is plausible. See [grounding drafts in a GitHub repo](/docs/grounding-drafts-in-github).
- **Product screenshots**, captured from your own app where the draft calls for one. See [screenshots in drafts](/docs/screenshots-in-drafts).

## Revising

Ask for a change to an existing document and the edits come back as **tracked suggestions**, not as replaced text. You read the diff and accept or reject, line by line or all at once.

This is deliberate, and it is the difference between a tool you can trust with a document and one you cannot: an assistant that rewrites in place is indistinguishable from losing your work.

## What it will not do

- **Publish.** Nothing reaches WordPress without a person pressing publish.
- **Edit without showing you.** Every AI change is a suggestion first.
- **Invent a source.** Where a draft is grounded in a repository or your existing docs, it works from those; where it is not, it is writing from the model’s general knowledge, and you should read it that way.

## Getting better results

The brief does most of the work. [Writing a good brief](/docs/writing-a-good-brief) is the highest-leverage page here — the difference between a two-line prompt and a proper brief is the difference between a draft you rewrite and one you edit.

## Related

- [Writing a good brief](/docs/writing-a-good-brief)
- [Style guides](/docs/style-guides)
- [Iterating on a draft](/docs/iterating-on-a-draft)