Muse for Writers and Editors: Outline-to-Draft Workflows, Fact-Check Passes, and a Style Sheet That Holds
A writer and editor setup for Muse: turn a brief into an outline you approve before drafting, run a fact-check pass that lists claims against sources, and…

Writing and editing fail in the handoffs. The outline promises one article, the draft delivers another, the fact-check happens from memory, and by the third revision nobody remembers whether the publication spells the product name with a hyphen or decided last month to drop it. The prose is rarely the hardest part. Keeping the brief, the sources, the style decisions, and the deadlines in one place is the job that eats the week.
This setup runs three jobs the same way on every piece. Muse turns a brief into an outline you approve before any drafting starts, runs a fact-check pass that lists each checkable claim against the source that supports it, and maintains a style sheet that records every decision as you make it. You keep the voice, the editorial calls, and the final read. Muse does the outlining, the claim listing, the consistency sweep, and the deadline list.
One rule holds the setup together. A draft is never its own source. A name, date, number, or quote comes from the source material you supplied, or it gets flagged as unverified. A style choice comes from the style sheet, or it gets flagged as a new decision for you to make.
The short version
- Approve an outline before drafting. Cutting a weak section at outline stage costs minutes, cutting it from a full draft costs an hour.
- Run fact-checking as a claim list, not a read-through. Each checkable claim gets a source, a verdict, and a fix if it fails.
- Keep a living style sheet per publication or client: spellings, capitalization, numbers, names, and banned phrases, updated at the moment you decide.
- Track revisions by version and open question, so a draft never circulates with an old decision baked in.
- The failure mode to watch for is a confident fact-check pass on a draft Muse wrote itself, and the fix is sources you supply plus a verdict of unverified when no source is in the file.
The Setup: The Second Desk
Call the whole arrangement the Second Desk. The example I run it against is Harborline, a three-person team that produces a weekly newsletter and two client white papers a month. The piece in this lesson is a 1,800-word explainer for a client, due Friday, with a first-draft deadline on Tuesday and an edit deadline on Thursday. Every job below runs on the same desk: the brief, the source folder, the style sheet, and the revision log, all kept together per piece.
The desk rests on the same pieces every time. A standing instruction from our memory guide holds the house rules: never present an unverified claim as checked, never change a quote, and never let a new style decision into a draft without logging it on the style sheet first. The brief follows the same discipline as a task brief written for an agent: outcome, audience, length, sources, and deadline stated up front, in writing. Deadline triage runs as a scheduled routine: a Monday list of every piece, its stage, and its next deadline.
Separate the deadlines the way editorial teams have long done it: one date for the first draft, one for the edit, and one for publication. A single Friday deadline hides the fact that the edit needs a finished draft on Tuesday to exist at all. The revision log shows the stage plainly: outline, draft, fact-check, style pass, approved.
Prompt 1: Turn the Brief Into an Outline You Approve
Run this before drafting, every time, even for pieces you could outline in your head. The brief states the angle, the audience, the word count, the sources, and the deadline. The outline is where you find out whether those five things agree with each other. A brief that asks for three case studies and a how-to section in 1,200 words does not agree with itself, and the outline is the cheapest place to learn that.
Have Muse draft section by section after the outline is approved, not the whole piece at once. A section you steer early keeps the next section on track, while a full draft generated from an unapproved outline gives you a polished version of the wrong article, and polishing is what makes wrong articles hard to cut.
Turn the brief below into an outline only. Do not draft any section. (1) Outline: a working title, the one-sentence promise to the reader, and each section with its heading, its point in one sentence, the source material it will draw on, and a target word count. The section word counts must add up to [total word count] or less. (2) Gaps: anything the brief asks for that the source material below does not support, listed as a gap, never filled from general knowledge. (3) Conflicts: any place where the brief and the sources disagree, or where two sources disagree with each other, flagged with both versions stated. (4) Questions for me: decisions the outline cannot make on its own, such as which example leads. Rules: every section must name its source. If a section has no source in the material below, mark it unsourced instead of outlining it as if it were supported.
Brief: [paste it]. Source material: [paste or attach it]. Audience and length: [state them].
Read the outline against the brief before you approve it, and watch for a section that restates the section before it, a word count that quietly grew by 400 words, or a claim in the promise that no source in the folder supports. Approve, cut, or reorder now. Then draft one section at a time, pasting the approved outline section and its sources back in each time, so the draft stays tied to the plan.
Prompt 2: Run the Fact-Check as a Claim List
Run this on the full draft, before the style pass. Fact-checking in editing has a settled shape. ACES, the society for editing, sets out the core method: verify each fact independently with more than one source, because one source can easily be wrong, and judge a source by its publisher and author, its own sources, and its date. Poynter’s guidance for editors adds the working habits: find at least two sources, ask the writer for source materials and check the text against them, and check every number and every calculation instead of assuming the math is right.
ACES notes from the editor’s side that how much fact-checking a job includes is not always clear, so settle the scope at the start of the project. For most newsletter and client work, the practical scope is names, titles, dates, numbers, quotes, and any claim a reader could repeat as fact. Opinions and recommendations are yours to judge, not claims to verify.
Run a fact-check pass on the draft below and return a claim list, not a rewrite. For every checkable claim, give: (1) the claim, quoted exactly from the draft, (2) the source in the material below that supports it, quoted or cited by document and line, (3) a verdict of supported, contradicted, or unverified, and (4) for contradicted or unverified claims, the smallest fix: correct it to what the source says, cut it, or mark it for me to verify. Check every name spelling, title, date, number, and quote, and redo any arithmetic in the draft yourself. Rules: a claim is supported only if a source I supplied supports it. Do not use your own knowledge as a source, and do not go looking for a source that agrees with the draft and report that as verification. If two supplied sources disagree, list the claim as contradicted and show both. Leave the draft text unchanged.
Draft: [paste it]. Source material: [paste or attach it, including recordings, notes, or documents the draft came from].
Work the list top to bottom and close each item in the draft or in the revision log. The list is the deliverable because it makes verification auditable. A week later you can show which claims were checked, against what, and what changed. A draft that came back with a general assurance that it reads accurately gives you nothing to check and nothing to file.
Prompt 3: Build the Style Sheet and Run the Consistency Pass
Run the first half when a publication or client relationship starts, and update it at the moment of each new decision. A style sheet is the copyeditor’s running record for one project: the spellings, capitalization, number and date treatment, names, and preferred terms chosen for this piece or this publication, on top of whatever general style guide the team follows. Editorial teams keep the sheet shared and update it as questions come in, so every editor on the piece is enforcing the same decisions.
Revision 2 fixes a term one way without a sheet, and revision 4 changes it back, because the second decision never reached the person, or the agent, doing the fourth pass. With a sheet, consistency stops depending on memory.
Build and maintain the style sheet for [publication or client], then run a consistency pass on the draft below. (1) Style sheet update: from the decisions list below, record each decision under spelling, capitalization, numbers and dates, names and titles, preferred terms, and phrases to avoid. If a decision in the list conflicts with one already on the sheet, flag the conflict and keep the sheet version until I rule. (2) Consistency pass: list every place the draft departs from the sheet, with the draft wording, the sheet wording, and the location, as a list of fixes for me to approve. Include inconsistent name spellings, number formats, and terms the sheet says to avoid. (3) New decisions: any recurring choice in the draft that the sheet does not cover, listed as a proposed sheet entry. Rules: do not edit the draft directly, and do not add a decision to the sheet that I have not made. Report the sheet and the fix list separately.
Current style sheet: [paste it, or write “none yet”]. Decisions made since the last pass: [list them]. Draft: [paste it].
Apply the approved fixes, add the new decisions you ruled on to the sheet, and log the version in the revision log: draft number, what changed, which claims in the fact-check list are still open, and the next deadline. That log is how the next piece starts faster, because the sheet and the open-question pattern carry over.
| Job | When | What it answers |
|---|---|---|
| Outline approval | Before drafting | Does every section have a point, a source, and a word count that fits the brief? |
| Section drafting | After outline approval, one section at a time | Does this section do what the outline promised, from the sources named for it? |
| Fact-check claim list | On the full draft, before the style pass | Which claims are supported, contradicted, or unverified, and what is the fix for each? |
| Style sheet pass | After the fact-check, and at every new decision | Does the draft match every recorded decision, and what new decisions need ruling? |
| Revision log and deadline sweep | Every Monday, and at every handoff | What version is current, what questions are open, and what is due next? |
What Can Go Wrong: Muse Fact-Checks Its Own Draft and Passes It
You ask for a draft, then ask for a fact-check of that same draft in the same session, with no source material supplied. The pass comes back clean. It comes back clean because the checker is grading its own work from the same memory that produced the errors, so a wrong date in the draft reads as familiar, and familiar reads as correct. The claim list, if you get one at all, marks claims supported without naming a source outside the draft itself.
The pattern matches our failure modes guide: a finished-looking result gets less checking than a rough one, and a self-approved fact-check is the most finished-looking result in the file. It has the shape of verification without the substance.
The fix has three parts, and all three are already in Prompt 2. First, supply the sources yourself: recordings, notes, documents, and published references. Require the verdict to quote or cite them. Second, accept unverified as a normal outcome: a claim with no supplied source gets flagged for you, not cleared. Third, where a claim matters, follow the ACES rule and verify it against a second, unconnected source yourself before it publishes. Muse runs the list, you own the verification it cannot do from the file alone.
Start With the Next Piece Already on Your Desk
Do not rebuild your whole editorial system this week. Take the next piece that is due, write its brief in five lines (angle, audience, length, sources, deadline), and run Prompt 1. Approve the outline, draft one section, then run Prompt 2 on that section as a test: the claim list will show you, on real work, whether your source folder is complete enough to check against.
If it holds for one piece, start the style sheet with the decisions that piece forced, and the desk is running.
Fact-checking method follows ACES, the society for editing: verify independently with more than one source, judge sources by publisher, author, sources used, and date, and settle the scope of fact-checking at the start of a project. Editor fact-checking habits follow Poynter: at least two sources, check text against the writer's source materials, and redo calculations. The style sheet description follows standard copyediting practice: a per-project running record of spelling, capitalization, number, name, and term decisions kept alongside the general style guide.


