gilde

← All craftbooks

Brand Tone Rewrite

Content and writingevalv1.0.0released 2026-06-05workflow: build-loop

Re-voice existing content to a specific brand tone while preserving every fact and the original structure: it first codifies the target voice into a concrete style guide — adjectives, do's and don'ts, banned and preferred words, sentence-length feel, point of view — then rewrites the content line by line to that voice without changing what it says. Covers tone of voice rewrite, rebranding copy, voice and tone, brand voice, re-voice content, and style adaptation. Codifying the voice into checkable rules before rewriting is the point: a small model that has explicit do/don't rules applies the tone consistently, instead of a vague 'make it friendlier' that drifts paragraph to paragraph.

Steps

Entry step: voice-scope. Each step names the specialist role it wants; the full working prompt is expandable.

  1. Voice scopeplannerentry

    codify the target tone into a concrete, checkable style guide

    Show working prompt
    1) Define the target voice in 3-5 adjectives (e.g. 'confident, warm, plain-spoken'). 2) Translate each adjective into 1-2 concrete rules (e.g. 'confident → no hedging words like maybe/perhaps'; 'plain-spoken → grade-8 reading level, no jargon'). 3) List banned words/phrases and preferred replacements. 4) Set point of view (first/second person), contraction policy, sentence-length feel, and how to handle CTAs. 5) Write or pick one before/after example sentence showing the transformation. Crucially, note what must NOT change: facts, claims, structure, and meaning. Write an acceptance-criteria checklist (e.g. 'every banned word removed'; 'POV/contractions consistent'; 'reading level on target'; 'no fact or section changed'; 'reads as one consistent voice'). Use write_task_note for the style guide + checklist, and write the same to the produces path. No rewrite yet.
  2. Rewrite to voicecopywriter

    re-voice the content to the style guide, preserving meaning

    Show working prompt
    Rewrite the content to the locked style guide. 1) Go section by section, preserving the original structure and headings exactly. 2) Apply every voice rule: remove banned words, use the specified POV and contraction policy, hit the target sentence feel and reading level. 3) Change HOW it reads, never WHAT it says — every fact, number, claim, and instruction must survive unchanged. 4) Keep the voice identical across the whole piece; no drift. 5) Output the rewritten content in the same format/markdown as the source. Save to the produces path and note which style rules you applied and confirm no facts changed.
  3. Evaluatereviewer

    Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.

    Show working prompt
    Compare tone-rewrite.md to the source and the style guide. Check EACH criterion and write PASS/FAIL: (a) every banned word/phrase is gone and preferred terms used; (b) POV, contraction policy, and reading level match the guide; (c) NO fact, number, claim, or section was changed or dropped (diff the meaning carefully — this is critical); (d) structure/headings preserved; (e) reads as one consistent voice with no drift. A rewrite that nails the tone but altered a fact FAILS — loop back to rewrite.

Then route — this is the whole point of the loop:

- **Every criterion PASSES →** call `advance_task_step({ ref, stepId: "evaluate", next: "finish" })`.
- **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: "evaluate", next: "rewrite" })` to loop back. The builder fixes exactly those gaps.

Never route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in.
  4. Finishdeveloper

    All acceptance criteria met. Stamp a short summary and report DONE.

    Show working prompt
    Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.

Triggers

Phrases that suggest this craftbook to a crew.

Source

View this craftbook on GitHub · MIT license