PlaysbyMoat8
Back to the library
The workflow guideMarketing

Edit expert posts using a style profile from past writing

Extract recurring stylistic choices from an expert’s own posts, then use that profile to edit new drafts while the expert remains the author.

6 implementation stepsSimple

How this works

Extract recurring stylistic choices from an expert’s own posts, then use that profile to edit new drafts while the expert remains the author. The goal is to reduce mechanical editing while preserving the expert's actual judgment. A useful style profile distinguishes stable habits from topic-specific wording and does not turn a handful of popular posts into rigid rules.

Separate meaning from presentation. First record the new draft's claims, qualifiers, and personal experiences; then edit structure and phrasing using a compact profile derived from permissioned writing. Return a diff and explain any substantive suggestion instead of silently changing the author's position.

Before you start

Representative writing

Use the author's own approved posts from several topics and dates, excluding ghostwritten exceptions unless identified.

Editing objective

Agree whether this pass improves clarity, length, structure, or channel formatting.

Author review

The author owns personal claims and resolves ambiguous intent before publication.

Prepare the inputs

writing_samples
Required

Text archive

Include source labels and dates; identify intentionally unusual styles.

new_draft
Required

Plain text

Preserve an untouched copy and the author's original claim sequence.

editing_brief
Required

Short instruction

Specify audience, channel, length, and permitted revision depth.

protected_meaning
Required

Claim list

Mark qualifications, quotations, experience statements, and wording that must survive.

optional_recent_feedback
Optional / conditional

Review notes

Distinguish explicit author preferences from editor assumptions.

Implementation, step by step

  1. Select the evidence

    • Choose a small balanced sample of original writing.
    • Tag recurring patterns in openings, sentence length, transitions, paragraphing, and endings.

    Checkpoint: Each proposed style observation points to more than one example or is labeled tentative.

  2. Build the profile

    • Describe a few actionable habits with short original illustrations.
    • Include disliked patterns and exceptions, avoiding claims that the model has been trained on the archive.

    Checkpoint: The profile is concise enough to review and update.

  3. Lock the meaning

    • Extract the new draft's central claim, evidence, caveats, and personal statements.
    • Flag ambiguous passages rather than resolving them through invented details.

    Checkpoint: The edit has a clear semantic baseline.

  4. Edit in two passes

    • First repair organization and clarity, then apply phrasing and formatting preferences.
    • Keep deliberate uncertainty and the author's actual level of confidence.

    Checkpoint: The revised post reads naturally without adding experience or certainty.

  5. Compare and annotate

    • Produce a readable before-and-after diff or a change table.
    • Label substantive alternatives as suggestions and explain why a fact or conclusion requires confirmation.

    Checkpoint: The author can inspect all changes that might affect meaning.

  6. Review and maintain

    • Incorporate approved feedback and deliver a clean version plus the diff.
    • Update the profile only when feedback indicates a recurring preference, not a one-off exception.

    Checkpoint: The final draft and the profile have separate version identifiers.

Decisions along the way

Samples conflict on tone

Use the subset closest to the current audience and label the scope of that choice.

The draft contains an unsupported personal claim

Preserve it as an author-confirmation question rather than embellishing or treating it as verified.

The requested length requires removing a caveat

Offer a longer version or a narrower claim; do not hide the limitation.

What you will produce

Style profile

Short document

A transparent editing guide grounded in the author's writing.

Include: scope · patterns · examples · exceptions · version

Edited draft and changes

Text plus diff

A publishable candidate whose substantive edits remain reviewable.

Include: original · revision · meaning_questions · change_reasons

Check the result

  • No new personal anecdote, metric, quotation, or customer claim appears.
  • Qualifiers such as sometimes and in this sample retain their meaning.
  • The opening matches the post's actual argument rather than promising more.
  • The author can reject a style preference without losing the untouched draft.

When something goes wrong

The revision sounds exaggerated or generic

Remove added rhetorical flourishes and return to the strongest observed patterns.

The archive is too small

Use a provisional profile and prioritize clarity; label voice matching as uncertain.

Repeated edits contradict author feedback

Revise the profile explicitly and rerun only affected sections.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Edit a short post about why onboarding checklists sometimes fail.

Inputs

Synthetic example. Six approved posts use concrete opening observations, short paragraphs, and qualified conclusions. The new draft says two pilot teams skipped a checklist; it does not claim all teams do.

Expected result

Synthetic expected result. The revision opens with the two-team observation, groups the explanation into short paragraphs, and keeps the limited sample explicit. A change note proposes a clearer ending while leaving the original anecdote intact. No broader failure rate is added.

Run a small pilot

Start small

Three new drafts by one author on a single channel.

Record the baseline

Record normal editing time and typical author revisions.

Agree success criteria

Measure author acceptance, meaning corrections, and time spent reviewing the diff.

Stop or revise

Pause profile reuse when the author repeatedly rejects its central voice assumptions.

Keep the scope clear

  • Use the author's approved material; do not impersonate unrelated writers or fabricate identity claims.
  • Editing produces a draft and does not authorize posting to the author's account.

Check before using

The author checks meaning and personal claims before publication. Updating examples is contextual guidance, not evidence of training a new model.

Business activities

  • Create and publish content

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: A representative archive of original posts · A new human-written draft

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗