51 Drafting and Rewriting Workflow Prompts for MIRENA

Use Drafting and Rewriting Workflow prompts when MIRENA needs to turn an approved brief into page copy or repair an existing page.

This workflow writes, rewrites, trims, expands, reorders, links, formats, and checks copy before the page moves into approval.

Start with source context.

Do not draft from a loose keyword, title, URL, competitor page, old post, or outline until MIRENA knows the site, offer, audience, page role, allowed topics, blocked topics, internal link rules, proof needs, and next workflow stage.

Use the source context template before this workflow if the project base is not ready. Use Getting Started with MIRENA if you need the full onboarding route first.

Start with Source Context Before Drafting or Rewriting

Source context controls the draft.

It tells MIRENA what the site is, who it serves, what it sells, which topics belong, which topics are blocked, which pages already exist, which routes support the offer, and which workflow should come next.

A draft can fail if it starts from a title, competitor article, old page, or keyword alone. The copy may look complete, but still drift away from the page role, repeat another URL, miss the user job, create weak internal links, or make claims that are not supported.

The Source Context page explains how source context protects topical focus before pages enter production.

Use source context to define:

site purpose
audience
offer
region
allowed topics
blocked topics
page role
protected pages
internal link targets
commercial routes
proof routes
support routes
comparison routes
writing constraints
output format
next workflow stage

When source context is missing, stop and build it first.

What Drafting and Rewriting Workflows Do

Drafting and Rewriting Workflows turn approved instructions into copy.

They do not collect raw discovery evidence.

They do not build the topical map.

They do not create the content brief.

They do not replace behavioral mapping.

They do not replace entity SEO.

They produce or repair the page.

The output can feed semantic internal linking when final link placement needs graph review. It can feed information gain work when the page needs stronger differentiation. It can feed SERP feature planning when snippet, FAQ, list, or table blocks need validation. It can feed schema cues only after the draft is approved.

Use MIRENA outputs when you need to define what the finished draft package should return.

A strong drafting or rewriting output should show:

the page title
the page role
the target user
the user job
the search intent
the approved section being drafted or repaired
the rewritten copy
proof added
examples added
internal links added
anchor direction
snippet or FAQ blocks
removed content
blocked items
revision notes
next workflow route

What This Page Does Not Repeat

This page does not repeat Raw Semantic Discovery prompts.

Raw Semantic Discovery collects candidates, modifiers, query paths, SERP patterns, competitor signals, and opportunity notes.

This page starts after approved inputs exist.

This page does not repeat Topical Maps + Planning prompts. Topical Mapping and Site Architecture decides pages, page roles, hierarchy, publishing order, and overlap controls.

This page does not repeat Behavioral Mapping and User Path prompts. Behavioral Mapping defines user state, journey stage, friction, trust, effort, next paths, and fallback paths.

This page does not repeat Content Brief Workflows. Content Briefs define page instructions before production.

This page also does not repeat Entity SEO prompts. Entity SEO handles entity meaning, salience, placement, relationships, and support cues.

Drafting and Rewriting Workflows use those outputs as approved inputs, then create or repair copy.

Use this page when the job is first draft, full rewrite, section repair, search intent repair, semantic drift repair, intro rewrite, heading rewrite, internal link rewrite, snippet formatting, FAQ repair, proof placement, CTA rewrite, readability repair, draft QA, approval, or handoff.

Use Semantic SEO when the draft also needs stronger meaning, context, and topic fit.

When to Use Drafting and Rewriting Workflow Prompts

Use this prompt collection when approved instructions need to become copy.

Drafting and Rewriting Workflows are useful for:

first drafts
full page rewrites
section rewrites
intro rewrites
heading rewrites
definition blocks
process blocks
comparison blocks
table blocks
FAQ blocks
PAA answers
snippet blocks
summary boxes
example blocks
proof blocks
CTA blocks
internal link placement
anchor text drafting
entity context integration
semantic drift repair
search intent repair
structure repair
repetition repair
flow repair
thin content expansion
content pruning
consolidation rewrites
docs rewrites
use case rewrites
comparison rewrites
product or service rewrites
draft QA
draft approval
production handoff

Use MIRENA inputs when you need to decide which files should feed the draft. Use the MIRENA workflow when the approved copy needs a clear route into internal linking, information gain, SERP feature validation, schema cues, publishing, or monitoring.

The Drafting and Rewriting Workflow

Run the Drafting and Rewriting Workflow in this order.

Set the draft scope.
Define the draft goal.
Review the production inputs.
Check source context fit.
Align the brief with the draft.
Align the outline with the draft.
Lock the page purpose.
Lock the search intent.
Lock the user job.
Plan copy around the page role.
Draft the first 100 words.
Draft the intro answer block.
Draft approved sections.
Expand approved headings.
Draft definition blocks.
Draft process blocks.
Draft comparison blocks.
Draft table blocks.
Draft FAQ blocks.
Draft PAA answers.
Draft snippet blocks.
Draft summary boxes.
Draft example blocks.
Draft proof blocks.
Draft CTA blocks.
Draft internal link placements.
Draft anchor text.
Integrate approved entity context.
Repair semantic drift.
Rewrite for search intent.
Rewrite structure.
Rewrite the intro.
Rewrite headings.
Rewrite sections.
Rewrite FAQs.
Rewrite tables.
Rewrite snippet blocks.
Rewrite PAA answers.
Rewrite internal link passages.
Rewrite conversion paths.
Rewrite support sections.
Repair mixed intent.
Repair repetition.
Repair choppy flow.
Expand thin content.
Prune clutter.
Rewrite consolidation pages.
Rewrite docs pages.
Rewrite use case pages.
Rewrite comparison pages.
Rewrite product or service pages.
Run draft QA.
Approve the draft.
Hand off the draft.

Do not move into publishing, schema cues, link implementation, or monitoring if purpose, proof, internal links, readability, blocked terms, approval status, or handoff route is unresolved.

The Drafting and Rewriting Prompt Pattern

Use short commands when the task is clear.

Use expanded prompts when the production step needs fields, constraints, section rules, links, proof, tone, QA, revision notes, and routing.

Short command pattern:

text

Run [drafting or rewrite module] for [page, draft, section, or URL].

Expanded prompt pattern:

text

Run [drafting or rewrite module] for [page, draft, section, or URL].

Use the source context first.

Use the approved brief, approved outline, map item, behavioral notes, entity notes, SERP notes, internal link plan, proof requirements, or existing URL only as evidence.

Return the output with these fields:
- page title
- URL or proposed URL
- page role
- target user
- user job
- search intent
- draft section
- rewritten section
- proof added
- internal links added
- anchor direction
- snippet or FAQ block
- blocked items
- revision notes
- next workflow route

Do not add off-scope topics.

Do not add unsupported claims.

Do not create schema before draft approval.

Route the final output into Draft QA, Internal Linking, Information Gain, SERP Feature Planning, Schema Cues after approval, or Draft Approval.

A short prompt is enough for a simple drafting task.

An expanded prompt is better when the input is large, risky, or ready for production handoff.

What to Give MIRENA Before Running Drafting or Rewriting

Start with source context.

Then add the strongest approved production input available.

For a first draft, give MIRENA:

source context
approved content brief
approved outline
page title
proposed URL
page role
target user
user job
search intent
section requirements
proof requirements
internal link requirements
CTA guidance
blocked terms

For a rewrite, give MIRENA:

source context
existing URL
current page copy
approved rewrite brief
target page role
target search intent
sections to keep
sections to revise
sections to remove
internal link updates
proof updates
CTA changes
blocked terms

For a section repair, give MIRENA:

source context
page role
approved brief
current section copy
section purpose
user job served
issue to repair
proof requirement
internal link requirement
target output format

For internal link rewriting, give MIRENA:

source context
current page copy
internal link plan
target pages
target page roles
anchor direction
surrounding passages
user path notes
link priority

For SERP formatting, give MIRENA:

source context
approved brief
target section
snippet target
FAQ requirement
table requirement
PAA questions
answer format
page experience risk notes

For proof and trust repair, give MIRENA:

source context
draft or section
claim list
proof requirements
evidence sources
trust gaps
proof placement notes
claims to remove or revise

Use rewrite for search intent when the existing page misses the query. Use fix semantic drift when the copy moves away from the page purpose. Use rewrite existing content when a live URL needs deeper repair. Use the rewrite checklist before approval.

Drafting and Rewriting Workflow Modules

The modules below create page copy, repair existing pages, prepare snippet blocks, add internal links, improve proof, clean readability, and route finished copy into approval and publication.

Choose the smallest module that fits the job.

1. Draft Scope

Use this to define what should be drafted or rewritten.

Short command:

text

Run Draft Scope for this page.

Expanded prompt:

text

Run Draft Scope for this page.

Use the source context first.

Define the production boundary before drafting or rewriting starts.

Return the output with these fields:
- page or URL
- draft type
- rewrite type
- approved inputs
- source inputs to use
- source inputs to ignore
- page role
- target user
- topics allowed
- topics blocked
- next workflow route

Do not draft yet.

Flag missing approved inputs.

Route the output into Draft Goal or Draft Input Review.

Best for:

first drafts
full rewrites
unclear production tasks
multiple input sets
risky rewrite requests

Output should include:

page or URL
draft type
approved inputs
allowed topics
blocked topics
next route

Use this to:

Set the production boundary before copy is written.

Draft Scope stops MIRENA from writing before the approved inputs are clear.

2. Draft Goal

Use this to define the production job.

Short command:

text

Run Draft Goal for this page.

Expanded prompt:

text

Run Draft Goal for this page.

Use the source context first.

Define the primary production goal.

Choose one main goal:
- new page draft
- full page rewrite
- section rewrite
- intro rewrite
- search intent repair
- semantic drift repair
- snippet rewrite
- FAQ rewrite
- table rewrite
- internal link rewrite
- proof rewrite
- CTA rewrite
- docs rewrite
- comparison rewrite
- use case rewrite

Return the output with these fields:
- primary draft goal
- secondary goals
- page role
- target user
- success criteria
- approved inputs needed
- risks before drafting
- next workflow route

Do not combine too many goals in one pass.

Route the output into Draft Input Review or Brief to Draft Alignment.

Best for:

unclear rewrite goals
mixed production tasks
editorial handoff
page repair
draft planning

Output should include:

primary draft goal
secondary goals
success criteria
risks
next route

Use this to:

Stop the production task from becoming too broad.

A full page rewrite, section repair, and snippet rewrite need different outputs.

3. Draft Input Review

Use this when several inputs may feed the draft.

Short command:

text

Run Draft Input Review on these files.

Expanded prompt:

text

Run Draft Input Review on these files.

Use the source context first.

Review the approved brief, outline, map item, entity notes, behavioral notes, link plan, SERP plan, analytics notes, existing page copy, and proof assets that may feed the draft.

Return the output with these fields:
- input name
- input type
- source quality
- production value
- risk
- use, hold, ignore, or review
- reason
- missing input
- next workflow route

Do not draft yet.

Separate production inputs from later QA inputs.

Route the output into Source Context to Draft Fit or Brief to Draft Alignment.

Best for:

several files
rewrite packages
existing content reviews
approved briefs with notes
complex production requests

Output should include:

input name
input type
production value
use or hold decision
next route

Use this to:

Select the inputs that should shape the draft.

Weak or unapproved inputs should not drive the production output.

4. Source Context to Draft Fit

Use this to check if the draft belongs in the site.

Short command:

text

Run Source Context to Draft Fit for this page.

Expanded prompt:

text

Run Source Context to Draft Fit for this page.

Use the source context first.

Check if the page, URL, section, or rewrite target fits the site, offer, audience, allowed topics, blocked topics, and workflow goal.

Return the output with these fields:
- page or section
- source context fit
- audience fit
- offer fit
- topic fit
- risk
- keep, revise, merge, hold, or block
- reason
- next workflow route

Do not draft a page or section that fails source context fit.

Route the output into Brief to Draft Alignment or Draft Approval.

Best for:

proposed drafts
old pages
competitor-led requests
keyword-led pages
risky sections

Output should include:

source context fit
audience fit
offer fit
action decision
next route

Use this to:

Prevent off-scope copy from entering production.

A page or section that fails source context fit should be revised, merged, held, or blocked.

5. Brief to Draft Alignment

Use this before drafting from an approved brief.

Short command:

text

Run Brief to Draft Alignment for this brief.

Expanded prompt:

text

Run Brief to Draft Alignment for this brief.

Use the source context first.

Check that the approved brief is ready for production.

Return the output with these fields:
- page title
- brief goal
- page role
- user job
- search intent
- required sections
- proof requirements
- internal link requirements
- blocked items
- drafting risks
- next workflow route

Do not draft if the brief lacks purpose, section requirements, proof rules, or link requirements.

Route the output into Outline to Draft Alignment or First 100 Words Draft.

Best for:

approved briefs
new page drafts
rewrite briefs
editorial handoff
draft readiness checks

Output should include:

brief goal
page role
required sections
proof rules
next route

Use this to:

Check the brief before production starts.

A draft should not begin from an incomplete brief.

6. Outline to Draft Alignment

Use this when an outline exists.

Short command:

text

Run Outline to Draft Alignment for this outline.

Expanded prompt:

text

Run Outline to Draft Alignment for this outline.

Use the source context first.

Check that the outline matches the approved brief before drafting.

Return the output with these fields:
- heading
- heading purpose
- required answer
- proof need
- internal link need
- SERP target
- overlap risk
- missing section
- section to remove
- next workflow route

Do not draft from an outline that drifts from the brief.

Route the output into Section Drafting or Heading Expansion.

Best for:

approved outlines
long pages
guides
comparison pages
docs pages

Output should include:

heading
heading purpose
missing section
section to remove
next route

Use this to:

Check heading structure before copy is written.

A weak outline creates weak drafting.

7. Page Purpose Lock

Use this to hold the draft to one clear job.

Short command:

text

Run Page Purpose Lock for this draft.

Expanded prompt:

text

Run Page Purpose Lock for this draft.

Use the source context first.

Lock the draft to the approved page purpose.

Return the output with these fields:
- page purpose
- primary job
- secondary support job
- user need
- page role
- section risks
- off-purpose content
- required fix
- next workflow route

Flag any section that does not serve the page purpose.

Route the output into Section Drafting, Structure Rewrite, or Draft QA.

Best for:

draft QA
weak rewrites
broad pages
section audits
production checks

Output should include:

page purpose
primary job
off-purpose content
required fix
next route

Use this to:

Keep the draft tied to one clear purpose.

Page Purpose Lock prevents sections from drifting into nearby topics.

8. Search Intent Lock

Use this to keep the draft aligned with intent.

Short command:

text

Run Search Intent Lock for this draft.

Expanded prompt:

text

Run Search Intent Lock for this draft.

Use the source context first.

Check that the draft or rewrite satisfies the approved search intent.

Return the output with these fields:
- primary intent
- secondary intent
- matching sections
- missing intent support
- mixed intent risk
- section to revise
- content to remove
- next workflow route

Do not force conflicting intent into one page.

Route the output into Search Intent Rewrite, Section Drafting, or Draft QA.

Best for:

search intent repair
existing pages
new drafts
snippet sections
mixed SERPs

Output should include:

primary intent
missing intent support
mixed intent risk
section to revise
next route

Use this to:

Keep the copy aligned with the approved query job.

Search Intent Lock should happen before final QA.

9. User Job Lock

Use this to keep the draft focused on the reader task.

Short command:

text

Run User Job Lock for this draft.

Expanded prompt:

text

Run User Job Lock for this draft.

Use the source context first.

Check that the draft helps the target user complete the approved job.

Return the output with these fields:
- target user
- user job
- user state
- task supported
- missing answer
- missing proof
- missing next step
- effort issue
- required fix
- next workflow route

Route the output into Section Drafting, Effort Repair, CTA Block Draft, or Draft QA.

Best for:

use case pages
docs pages
product pages
support pages
conversion pages

Output should include:

target user
user job
missing answer
missing proof
required fix

Use this to:

Make the draft useful for the reader task.

A page can cover a topic and still fail the user job.

10. Page Role Draft Plan

Use this to make the copy fit the page’s site role.

Short command:

text

Run Page Role Draft Plan for this page.

Expanded prompt:

text

Run Page Role Draft Plan for this page.

Use the source context first.

Plan how the draft should reflect its page role.

Return the output with these fields:
- page role
- role reason
- required copy behavior
- required internal links
- support pages
- CTA route
- proof need
- section priority
- next workflow route

Use the page role to guide copy, links, proof, and CTA timing.

Route the output into Section Drafting or Internal Link Placement Draft.

Best for:

hub pages
spoke pages
support pages
comparison pages
conversion support pages

Output should include:

page role
required copy behavior
required links
proof need
next route

Use this to:

Make the copy fit the page’s role in the site.

A hub, support page, docs page, and conversion page should not read the same way.

11. First 100 Words Draft

Use this to write the opening with the primary entity and core answer.

Short command:

text

Draft the first 100 words for this page.

Expanded prompt:

text

Draft the first 100 words for this page.

Use the source context first.

Use the approved brief and outline.

Write an opening that introduces the primary entity, satisfies the core query intent, and gives the reader a clear reason to continue.

Return the output with these fields:
- opening draft
- primary entity included
- intent satisfied
- user job served
- proof or next step cue
- revision note
- next workflow route

Keep the opening direct.

Do not use filler framing.

Route the output into Intro Answer Block or Draft QA.

Best for:

new drafts
intro repair
snippet-focused pages
definitions
use case pages

Output should include:

opening draft
primary entity note
user job note
revision note
next route

Use this to:

Start the page with clear purpose and intent fit.

The opening should not delay the core answer.

12. Intro Answer Block

Use this when the page needs a direct opening answer.

Short command:

text

Draft the Intro Answer Block for this page.

Expanded prompt:

text

Draft the Intro Answer Block for this page.

Use the source context first.

Write a concise answer block that states what the page covers and gives the reader the core answer early.

Return the output with these fields:
- answer block
- target question
- primary entity
- user job served
- snippet fit
- proof cue
- next workflow route

Keep the answer clear and extractable.

Route the output into Section Drafting or Snippet Block Draft.

Best for:

answer-led pages
docs pages
definition pages
support pages
snippet targets

Output should include:

answer block
target question
primary entity
snippet fit
next route

Use this to:

Give the reader a direct answer early.

Intro Answer Block can also support paragraph snippets.

13. Section Drafting

Use this to draft one approved section.

Short command:

text

Draft this section from the approved brief.

Expanded prompt:

text

Draft this section from the approved brief.

Use the source context first.

Write only the requested section.

Return the output with these fields:
- section heading
- section draft
- section purpose
- user job served
- required points covered
- proof added
- internal link added
- revision note
- next workflow route

Do not draft other sections.

Do not add off-scope ideas.

Route the output into Section QA, Internal Link Placement Draft, or Draft QA.

Best for:

approved outlines
long pages
controlled drafting
section repair
editorial workflows

Output should include:

section heading
section draft
purpose
proof added
next route

Use this to:

Draft one approved section without changing the page plan.

Section Drafting keeps production controlled.

14. Heading Expansion

Use this when headings need copy under them.

Short command:

text

Expand these headings into draft sections.

Expanded prompt:

text

Expand these headings into draft sections.

Use the source context first.

Draft copy under each approved heading.

Return the output with these fields:
- heading
- section draft
- section role
- answer covered
- proof added
- internal link added
- risk note
- next workflow route

Keep each heading focused on one job.

Route the output into Section Rewrite or Draft QA.

Best for:

approved outlines
bulk drafting
section expansion
guides
docs pages

Output should include:

heading
section draft
section role
proof added
next route

Use this to:

Turn approved headings into focused copy.

Heading Expansion should not introduce new unapproved sections.

15. Definition Block Draft

Use this for definition pages or direct answer sections.

Short command:

text

Draft a Definition Block for this term.

Expanded prompt:

text

Draft a Definition Block for this term.

Use the source context first.

Write a clear definition that fits the page purpose and user job.

Return the output with these fields:
- term
- definition
- plain language explanation
- example if needed
- internal link need
- snippet fit
- next workflow route

Do not create a vague glossary answer.

Route the output into Snippet Block Draft or Draft QA.

Best for:

definition pages
semantic SEO pages
docs pages
glossary sections
snippet targets

Output should include:

term
definition
plain explanation
example
next route

Use this to:

Create a clear definition that supports the page purpose.

A definition should help the reader continue through the page.

16. Process Block Draft

Use this for steps, workflows, and how-to sections.

Short command:

text

Draft a Process Block for this section.

Expanded prompt:

text

Draft a Process Block for this section.

Use the source context first.

Write clear steps for the approved process.

Return the output with these fields:
- process title
- step list
- required inputs
- expected output
- support note
- proof note
- next workflow route

Keep steps sequential.

Route the output into Snippet Block Draft, FAQ Block Draft, or Draft QA.

Best for:

how-to pages
docs pages
workflows
onboarding pages
support pages

Output should include:

process title
step list
inputs
expected output
next route

Use this to:

Turn process requirements into clear steps.

A process block should help the user act.

17. Comparison Block Draft

Use this for choice, alternatives, or criteria sections.

Short command:

text

Draft a Comparison Block for this page.

Expanded prompt:

text

Draft a Comparison Block for this page.

Use the source context first.

Write a balanced comparison that supports the buyer question.

Return the output with these fields:
- comparison topic
- options compared
- criteria
- comparison copy
- proof need
- decision cue
- CTA or fallback path
- next workflow route

Do not force a weak winner.

Route the output into Table Block Draft, Proof Block Draft, or Draft QA.

Best for:

comparison pages
alternatives pages
product pages
buyer guides
commercial investigation pages

Output should include:

comparison topic
criteria
comparison copy
decision cue
next route

Use this to:

Help users choose with fair, clear criteria.

Comparison blocks should reduce uncertainty.

18. Table Block Draft

Use this when a table helps the reader compare or scan.

Short command:

text

Draft a Table Block for this page.

Expanded prompt:

text

Draft a Table Block for this page.

Use the source context first.

Create a simple table only if it reduces effort.

Return the output with these fields:
- table purpose
- columns
- rows
- table copy
- summary sentence
- proof need
- risk note
- next workflow route

Keep cells short.

Add a short explanation before or after the table.

Route the output into Draft QA or SERP Feature Planning.

Best for:

comparison pages
decision pages
docs pages
feature pages
snippet targets

Output should include:

table purpose
columns
rows
summary sentence
next route

Use this to:

Make information easier to compare or scan.

Do not use a table when prose is clearer.

19. FAQ Block Draft

Use this for useful follow-up questions.

Short command:

text

Draft the FAQ Block for this page.

Expanded prompt:

text

Draft the FAQ Block for this page.

Use the source context first.

Write FAQs that support the page role and user path.

Return the output with these fields:
- FAQ question
- short answer
- user state served
- internal link need
- schema cue eligibility after approval
- risk note
- next workflow route

Do not add filler FAQs.

Route the output into Draft QA or Schema Cues after approval.

Best for:

support pages
product pages
comparison pages
docs pages
PAA targets

Output should include:

FAQ question
short answer
user state served
link need
next route

Use this to:

Answer real follow-up questions.

FAQ blocks should support the page role and next path.

20. PAA Answer Draft

Use this for People Also Ask style answers.

Short command:

text

Draft PAA answers for this page.

Expanded prompt:

text

Draft PAA answers for this page.

Use the source context first.

Write short answers for the approved PAA questions.

Return the output with these fields:
- PAA question
- answer
- answer format
- section placement
- internal link need
- risk note
- next workflow route

Keep each answer direct.

Route the output into FAQ Block Draft, Snippet Block Draft, or Draft QA.

Best for:

PAA sections
FAQ sections
snippet planning
support pages
informational pages

Output should include:

question
answer
format
placement
next route

Use this to:

Create clear follow-up answers that fit the page.

PAA answers should be useful on the page, not only for search display.

21. Snippet Block Draft

Use this for paragraph, list, or table snippet blocks.

Short command:

text

Draft Snippet Blocks for this page.

Expanded prompt:

text

Draft Snippet Blocks for this page.

Use the source context first.

Write extractable answer blocks that also help the reader.

Return the output with these fields:
- snippet target
- snippet type
- block draft
- target question
- section placement
- supporting detail
- risk note
- next workflow route

Use paragraph, ordered list, unordered list, definition, or table format only where it fits.

Route the output into Draft QA or SERP Feature Planning.

Best for:

featured snippet targets
direct answers
process lists
definitions
tables

Output should include:

snippet target
snippet type
block draft
placement
next route

Use this to:

Create extractable blocks without weakening the page experience.

Snippet blocks should still help the reader.

22. Summary Box Draft

Use this when the page needs a fast answer or recap.

Short command:

text

Draft a Summary Box for this page.

Expanded prompt:

text

Draft a Summary Box for this page.

Use the source context first.

Write a summary box that reduces reading effort.

Return the output with these fields:
- box title
- summary bullets
- user job served
- placement
- internal link need
- risk note
- next workflow route

Keep the box short and useful.

Route the output into Draft QA.

Best for:

long guides
docs pages
decision pages
comparison pages
support pages

Output should include:

box title
summary bullets
placement
link need
next route

Use this to:

Reduce reading effort with a short useful recap.

Summary boxes should support the reader’s next step.

23. Example Block Draft

Use this when the reader needs a practical example.

Short command:

text

Draft an Example Block for this page.

Expanded prompt:

text

Draft an Example Block for this page.

Use the source context first.

Write an example that supports the section and user job.

Return the output with these fields:
- example title
- example copy
- task served
- proof or source need
- internal link need
- risk note
- next workflow route

Do not add examples that distract from the page purpose.

Route the output into Draft QA.

Best for:

docs pages
prompt pages
how-to pages
use case pages
templates

Output should include:

example title
example copy
task served
source need
next route

Use this to:

Make abstract guidance easier to apply.

An example should serve the section job.

24. Proof Block Draft

Use this when claims need support.

Short command:

text

Draft a Proof Block for this page.

Expanded prompt:

text

Draft a Proof Block for this page.

Use the source context first.

Write proof support for the approved claim or section.

Return the output with these fields:
- claim supported
- proof copy
- evidence source
- placement
- trust need served
- risk if missing
- next workflow route

Do not create unsupported claims.

Route the output into Draft QA or Proof Review.

Best for:

commercial pages
comparison pages
product pages
service pages
trust-heavy sections

Output should include:

claim supported
proof copy
evidence source
placement
next route

Use this to:

Support claims before approval.

Proof blocks should make the page more credible and safer.

25. CTA Block Draft

Use this when the page needs a next step.

Short command:

text

Draft the CTA Block for this page.

Expanded prompt:

text

Draft the CTA Block for this page.

Use the source context first.

Write a CTA that matches user readiness, page role, and next path.

Return the output with these fields:
- CTA copy
- CTA purpose
- placement
- user readiness
- trust need before CTA
- fallback path
- risk note
- next workflow route

Do not push action before the page has earned it.

Route the output into Draft QA.

Best for:

product pages
service pages
use case pages
comparison pages
conversion support pages

Output should include:

CTA copy
purpose
placement
readiness
fallback path

Use this to:

Add a next step that fits the user’s readiness.

CTA copy should feel earned by the page.

26. Internal Link Placement Draft

Use this when links need to be written into the copy.

Short command:

text

Draft internal link placements for this page.

Expanded prompt:

text

Draft internal link placements for this page.

Use the source context first.

Place required internal links inside relevant passages.

Return the output with these fields:
- source passage
- target page
- link purpose
- anchor direction
- placement
- user path served
- page role supported
- next workflow route

Do not add generic links.

Route the output into Anchor Text Draft or Internal Link Rewrite.

Best for:

approved briefs with link targets
rewrites
cluster pages
hub pages
support pages

Output should include:

source passage
target page
link purpose
anchor direction
next route

Use this to:

Write internal links where they help the reader.

Use semantic internal linking when final link placement needs architecture and entity review.

27. Anchor Text Draft

Use this when anchor wording needs to match the next action.

Short command:

text

Draft anchor text for these internal links.

Expanded prompt:

text

Draft anchor text for these internal links.

Use the source context first.

Write anchor text that matches the surrounding sentence and target page promise.

Return the output with these fields:
- target page
- anchor text
- anchor intent
- surrounding sentence
- risk note
- next workflow route

Avoid exact-match repetition.

Do not overpromise the target.

Route the output into Draft QA or Internal Linking.

Best for:

internal link updates
rewrite tasks
page refresh
hub and spoke links
support paths

Output should include:

target page
anchor text
anchor intent
surrounding sentence
next route

Use this to:

Write anchors that describe the next step.

Use anchor text by intent when the anchor system needs deeper planning.

28. Entity Context Integration

Use this when approved entity notes need to appear in the draft.

Short command:

text

Integrate approved entity context into this draft.

Expanded prompt:

text

Integrate approved entity context into this draft.

Use the source context first.

Use approved entity notes as writing guidance only.

Return the output with these fields:
- primary entity placement
- supporting entity placement
- section updated
- relationship clarified
- term avoided
- revision note
- next workflow route

Do not run entity salience.

Do not create schema.

Route the output into Draft QA or Entity SEO and Salience if deeper work is needed.

Best for:

semantic SEO pages
entity-heavy drafts
product pages
comparison pages
docs pages

Output should include:

primary entity placement
supporting entity placement
relationship note
revision note
next route

Use this to:

Add approved entity context into copy without turning drafting into an entity audit.

Use Entity SEO if deeper entity structure is needed.

29. Semantic Drift Repair

Use this when the draft moves away from the approved topic.

Short command:

text

Run Semantic Drift Repair on this draft.

Expanded prompt:

text

Run Semantic Drift Repair on this draft.

Use the source context first.

Find and repair copy that drifts from the page purpose, primary entity, user job, or approved brief.

Return the output with these fields:
- drift section
- drift type
- source context issue
- revised copy
- removed copy
- reason
- next workflow route

Do not broaden the page.

Route the output into Draft QA.

Best for:

broad drafts
old articles
rewritten pages
AI-assisted copy
semantic SEO pages

Output should include:

drift section
drift type
revised copy
removed copy
next route

Use this to:

Pull the copy back to the approved page purpose.

Use fix semantic drift when an existing page needs deeper drift repair.

30. Search Intent Rewrite

Use this when the page misses the query.

Short command:

text

Run Search Intent Rewrite on this page.

Expanded prompt:

text

Run Search Intent Rewrite on this page.

Use the source context first.

Rewrite the sections that fail the approved search intent.

Return the output with these fields:
- current section
- intent issue
- revised section
- answer added
- format change
- proof added
- next workflow route

Do not change the page into a different intent target.

Route the output into Draft QA.

Best for:

search intent mismatch
old pages
refreshes
snippet pages
mixed SERPs

Output should include:

current section
intent issue
revised section
answer added
next route

Use this to:

Repair the copy so it satisfies the approved intent.

Use rewrite for search intent when a page needs a focused intent repair pass.

31. Structure Rewrite

Use this when the page is hard to follow.

Short command:

text

Run Structure Rewrite on this page.

Expanded prompt:

text

Run Structure Rewrite on this page.

Use the source context first.

Rewrite the page structure so the order, headings, sections, summaries, examples, links, and CTAs support the user job.

Return the output with these fields:
- current structure issue
- revised order
- revised heading
- revised section
- removed section
- link placement
- next workflow route

Do not add new topics unless approved.

Route the output into Draft QA.

Best for:

hard-to-follow pages
long guides
old content
docs pages
comparison pages

Output should include:

structure issue
revised order
revised heading
removed section
next route

Use this to:

Make the page easier to follow.

Structure Rewrite improves order before polishing wording.

32. Intro Rewrite

Use this when the opening is weak.

Short command:

text

Run Intro Rewrite on this page.

Expanded prompt:

text

Run Intro Rewrite on this page.

Use the source context first.

Rewrite the opening so it answers faster, names the primary entity, states the page purpose, and sets the next path.

Return the output with these fields:
- original intro issue
- revised intro
- primary entity used
- user job served
- snippet fit
- next workflow route

Remove filler.

Route the output into Draft QA.

Best for:

weak openings
broad introductions
old posts
snippet targets
search intent repair

Output should include:

original issue
revised intro
primary entity note
user job note
next route

Use this to:

Make the opening faster and clearer.

An intro should not delay the answer.

33. Heading Rewrite

Use this when headings are vague or misaligned.

Short command:

text

Run Heading Rewrite on this page.

Expanded prompt:

text

Run Heading Rewrite on this page.

Use the source context first.

Rewrite headings so each one serves a clear section job.

Return the output with these fields:
- current heading
- heading issue
- revised heading
- heading purpose
- user job served
- SERP target if any
- next workflow route

Do not add clever headings that reduce clarity.

Route the output into Section Rewrite or Draft QA.

Best for:

vague outlines
old pages
readability repair
section repair
snippet planning

Output should include:

current heading
heading issue
revised heading
purpose
next route

Use this to:

Make headings clear and useful.

Headings should help readers and search systems understand the section job.

34. Section Rewrite

Use this when a section is weak, unclear, or off-purpose.

Short command:

text

Run Section Rewrite on this section.

Expanded prompt:

text

Run Section Rewrite on this section.

Use the source context first.

Rewrite the section to match the approved brief, user job, and page role.

Return the output with these fields:
- original section
- issue
- revised section
- proof added
- internal link added
- removed content
- revision note
- next workflow route

Do not change the section purpose without review.

Route the output into Draft QA.

Best for:

weak sections
outdated sections
section-level rewrites
proof repair
link insertion

Output should include:

original section
issue
revised section
proof added
next route

Use this to:

Repair one section while keeping the page plan intact.

Section Rewrite is useful when only part of the page needs work.

35. FAQ Rewrite

Use this when FAQs are weak or filler.

Short command:

text

Run FAQ Rewrite on this page.

Expanded prompt:

text

Run FAQ Rewrite on this page.

Use the source context first.

Rewrite FAQs so they answer real follow-up questions and support the page role.

Return the output with these fields:
- current FAQ
- issue
- revised FAQ
- user state served
- internal link need
- schema cue eligibility after approval
- next workflow route

Remove filler FAQs.

Route the output into Draft QA or Schema Cues after approval.

Best for:

filler FAQs
PAA repair
support pages
product pages
schema cue prep

Output should include:

current FAQ
issue
revised FAQ
user state
next route

Use this to:

Make FAQs useful and page-specific.

FAQs should not be added only for length.

36. Table Rewrite

Use this when a table is unclear or too heavy.

Short command:

text

Run Table Rewrite on this page.

Expanded prompt:

text

Run Table Rewrite on this page.

Use the source context first.

Rewrite the table so users can scan, compare, or choose faster.

Return the output with these fields:
- current table issue
- revised columns
- revised rows
- summary sentence
- proof need
- placement note
- next workflow route

Do not use a table if prose is clearer.

Route the output into Draft QA.

Best for:

comparison pages
feature pages
docs pages
buyer guides
dense content

Output should include:

table issue
revised columns
revised rows
summary sentence
next route

Use this to:

Make table content easier to use.

A table should reduce effort and support a choice.

37. Snippet Rewrite

Use this when a page needs better snippet formatting.

Short command:

text

Run Snippet Rewrite on this page.

Expanded prompt:

text

Run Snippet Rewrite on this page.

Use the source context first.

Rewrite answer blocks, lists, tables, or definitions for better extractability and reader value.

Return the output with these fields:
- snippet target
- current issue
- revised block
- format type
- section placement
- support detail
- next workflow route

Do not make the page worse for users to chase a feature.

Route the output into Draft QA or SERP Feature Planning.

Best for:

paragraph snippets
list snippets
definition blocks
table snippets
SERP feature repair

Output should include:

snippet target
current issue
revised block
format type
next route

Use this to:

Improve extractable answers without harming the page.

Snippet Rewrite should support reader value first.

38. PAA Rewrite

Use this when PAA answers need clearer follow-up coverage.

Short command:

text

Run PAA Rewrite on this page.

Expanded prompt:

text

Run PAA Rewrite on this page.

Use the source context first.

Rewrite PAA style answers so they give useful short responses and guide the next step.

Return the output with these fields:
- question
- current answer issue
- revised answer
- internal link need
- section placement
- next workflow route

Keep answers direct and useful.

Route the output into FAQ Rewrite or Draft QA.

Best for:

PAA sections
FAQ blocks
support pages
old pages
answer cleanup

Output should include:

question
issue
revised answer
link need
next route

Use this to:

Make short answers more useful and connected.

PAA answers should not become isolated fragments.

39. Internal Link Rewrite

Use this when links need better placement or anchor context.

Short command:

text

Run Internal Link Rewrite on this page.

Expanded prompt:

text

Run Internal Link Rewrite on this page.

Use the source context first.

Rewrite passages so internal links fit the user path and target page promise.

Return the output with these fields:
- current passage
- target page
- anchor issue
- revised passage
- revised anchor
- link purpose
- next workflow route

Do not insert links without context.

Route the output into Draft QA or Semantic Internal Linking.

Best for:

existing pages
internal link refreshes
anchor repair
hub and spoke links
support paths

Output should include:

current passage
target page
anchor issue
revised passage
next route

Use this to:

Make internal links fit naturally inside the copy.

Use rewrite for internal links when the page needs deeper link path repair.

40. Conversion Path Rewrite

Use this when the page needs a clearer next action.

Short command:

text

Run Conversion Path Rewrite on this page.

Expanded prompt:

text

Run Conversion Path Rewrite on this page.

Use the source context first.

Rewrite copy so the next action appears after enough clarity, proof, and user value.

Return the output with these fields:
- current conversion issue
- revised section
- CTA copy
- proof added
- fallback path
- risk note
- next workflow route

Do not push conversion too early.

Route the output into Draft QA.

Best for:

product pages
service pages
pricing support pages
use case pages
comparison pages

Output should include:

conversion issue
revised section
CTA copy
proof added
next route

Use this to:

Make conversion copy feel earned and useful.

The CTA should fit user readiness.

41. Support Section Rewrite

Use this when support content fails the task.

Short command:

text

Run Support Section Rewrite on this support page.

Expanded prompt:

text

Run Support Section Rewrite on this support page.

Use the source context first.

Rewrite support copy so the user can complete the task.

Return the output with these fields:
- support task
- current issue
- revised steps
- missing input
- expected output
- fallback path
- next workflow route

Keep the rewrite task-focused.

Route the output into Draft QA.

Best for:

docs pages
onboarding pages
support pages
troubleshooting sections
workflow instructions

Output should include:

support task
issue
revised steps
missing input
expected output

Use this to:

Repair support content so the user can finish the task.

Support sections should be sequential and clear.

42. Mixed Intent Rewrite

Use this when the page tries to serve conflicting goals.

Short command:

text

Run Mixed Intent Rewrite on this page.

Expanded prompt:

text

Run Mixed Intent Rewrite on this page.

Use the source context first.

Repair sections that combine conflicting intents.

Return the output with these fields:
- mixed intent section
- intent conflict
- revised section
- content to move
- content to remove
- better target page
- next workflow route

Do not force two incompatible jobs into one page.

Route the output into Draft QA or Topical Mapping if page structure needs review.

Best for:

old pages
keyword-led pages
overexpanded pages
broad guides
confusing landing pages

Output should include:

mixed intent section
conflict
revised section
content to move
next route

Use this to:

Separate conflicting page jobs.

Some mixed intent problems need map review before rewriting continues.

43. Repetition Repair

Use this when the page repeats itself.

Short command:

text

Run Repetition Repair on this draft.

Expanded prompt:

text

Run Repetition Repair on this draft.

Use the source context first.

Find repeated phrases, repeated claims, repeated sections, repeated examples, and repeated transitions.

Return the output with these fields:
- repeated text
- repetition type
- revised copy
- removed copy
- merged idea
- revision note
- next workflow route

Keep necessary entity reinforcement.

Remove lazy repetition.

Route the output into Draft QA.

Best for:

long drafts
AI-assisted copy
refreshes
repeated examples
awkward transitions

Output should include:

repeated text
repetition type
revised copy
removed copy
next route

Use this to:

Remove waste while keeping needed reinforcement.

Repetition Repair should make the page tighter and clearer.

44. Choppy Flow Repair

Use this when the draft feels disconnected.

Short command:

text

Run Choppy Flow Repair on this draft.

Expanded prompt:

text

Run Choppy Flow Repair on this draft.

Use the source context first.

Repair passage flow, transitions, section order, and sentence rhythm.

Return the output with these fields:
- flow issue
- affected passage
- revised passage
- transition added
- section order note
- next workflow route

Keep sentences clear.

Do not add filler transitions.

Route the output into Draft QA.

Best for:

rough drafts
sectioned outlines
rewritten pages
long guides
docs pages

Output should include:

flow issue
affected passage
revised passage
transition note
next route

Use this to:

Make the draft read smoothly without adding fluff.

Flow repair should connect ideas, not pad the page.

45. Thin Content Expansion

Use this when a section lacks useful depth.

Short command:

text

Run Thin Content Expansion on this section.

Expanded prompt:

text

Run Thin Content Expansion on this section.

Use the source context first.

Expand the section only where depth helps the user and supports the brief.

Return the output with these fields:
- thin section
- missing detail
- added copy
- example added
- proof added
- internal link added
- next workflow route

Do not pad the page.

Route the output into Draft QA.

Best for:

thin sections
weak drafts
missing examples
incomplete explanations
support gaps

Output should include:

thin section
missing detail
added copy
proof added
next route

Use this to:

Add useful depth where the brief requires it.

Expansion should serve the user job.

46. Content Pruning

Use this when the draft contains clutter or off-scope copy.

Short command:

text

Run Content Pruning on this draft.

Expanded prompt:

text

Run Content Pruning on this draft.

Use the source context first.

Remove or move copy that weakens page focus.

Return the output with these fields:
- content to remove
- reason
- better destination
- revised passage
- source context note
- next workflow route

Do not remove copy that supports the page purpose.

Route the output into Draft QA.

Best for:

overlong drafts
off-scope sections
broad pages
duplicate content
rewrite cleanup

Output should include:

content to remove
reason
better destination
revised passage
next route

Use this to:

Cut clutter and protect page focus.

Content Pruning should not remove useful depth.

47. Consolidation Rewrite

Use this when several pages or sections need merging.

Short command:

text

Run Consolidation Rewrite for these pages.

Expanded prompt:

text

Run Consolidation Rewrite for these pages.

Use the source context first.

Rewrite overlapping content into one canonical page or section.

Return the output with these fields:
- source pages
- canonical target
- content kept
- content removed
- merged section
- redirect note
- internal link update
- next workflow route

Do not merge separate intent.

Route the output into Draft QA or Internal Linking.

Best for:

duplicate pages
cannibalization repair
site restructures
old blog cleanup
merge briefs

Output should include:

source pages
canonical target
content kept
content removed
next route

Use this to:

Merge overlap without losing useful content.

Consolidation Rewrite should protect distinct intent.

48. Docs Rewrite

Use this when documentation needs clearer task flow.

Short command:

text

Run Docs Rewrite on this page.

Expanded prompt:

text

Run Docs Rewrite on this page.

Use the source context first.

Rewrite documentation so the user can follow the task from input to output.

Return the output with these fields:
- user task
- rewritten intro
- rewritten steps
- inputs needed
- output expected
- support path
- fallback path
- next workflow route

Keep the page sequential.

Route the output into Draft QA.

Best for:

onboarding pages
help docs
product workflows
support pages
troubleshooting pages

Output should include:

user task
rewritten steps
inputs
output
next route

Use this to:

Make documentation clear and task-focused.

Docs Rewrite should guide users from setup to output.

49. Use Case Rewrite

Use this when a use case page needs clearer product fit.

Short command:

text

Run Use Case Rewrite on this page.

Expanded prompt:

text

Run Use Case Rewrite on this page.

Use the source context first.

Rewrite the page around the user job, problem, outcome, product fit, proof, and next path.

Return the output with these fields:
- use case
- user job
- rewritten sections
- proof added
- product fit clarified
- CTA or fallback path
- next workflow route

Do not make the use case generic.

Route the output into Draft QA.

Best for:

SaaS use cases
product-led pages
service use cases
workflow pages
audience pages

Output should include:

use case
user job
rewritten sections
product fit
next route

Use this to:

Make use case copy specific and outcome-led.

The rewrite should connect user problem to product fit.

50. Comparison Rewrite

Use this when a comparison page needs clearer criteria and proof.

Short command:

text

Run Comparison Rewrite on this page.

Expanded prompt:

text

Run Comparison Rewrite on this page.

Use the source context first.

Rewrite the comparison so the buyer can choose with better clarity.

Return the output with these fields:
- comparison topic
- buyer question
- rewritten criteria
- rewritten table
- proof added
- decision guidance
- CTA or fallback path
- next workflow route

Keep the comparison fair.

Route the output into Draft QA.

Best for:

alternatives pages
product comparisons
buyer guides
commercial investigation pages
vs pages

Output should include:

comparison topic
buyer question
criteria
proof added
next route

Use this to:

Make comparison copy fair, useful, and decision-led.

The buyer should understand the criteria and next step.

51. Product or Service Rewrite

Use this when an offer page needs clearer value and proof.

Short command:

text

Run Product or Service Rewrite on this page.

Expanded prompt:

text

Run Product or Service Rewrite on this page.

Use the source context first.

Rewrite the page so the offer, audience, problem, benefits, proof, objections, support links, and CTA path are clear.

Return the output with these fields:
- offer
- target audience
- rewritten value section
- proof added
- objection handled
- support link added
- CTA path
- next workflow route

Flag unsupported claims.

Route the output into Draft QA.

Best for:

product pages
service pages
SaaS pages
offer pages
conversion support pages

Output should include:

offer
audience
value section
proof added
next route

Use this to:

Make offer copy clearer, supported, and useful.

Product and service rewrites should connect value to proof.

52. Draft QA

Use this before draft approval.

Short command:

text

Run Draft QA on this page.

Expanded prompt:

text

Run Draft QA on this page.

Use the source context first.

Audit the draft before approval.

Return the output with these fields:
- source context fit
- page purpose fit
- search intent fit
- user job fit
- section completeness
- proof gaps
- internal link gaps
- anchor issues
- snippet readiness
- readability issues
- blocked term issues
- required fixes
- next workflow route

Do not approve drafts with unresolved purpose, proof, link, readability, or blocked term issues.

Route the output into Draft Approval or revision.

Best for:

final draft checks
rewrites
high value pages
editorial approval
production QA

Output should include:

fit checks
proof gaps
link gaps
readability issues
required fixes

Use this to:

Catch production issues before final approval.

Draft QA should happen before schema cues or publishing.

53. Draft Approval

Use this when the draft is ready for final review.

Short command:

text

Run Draft Approval on this page.

Expanded prompt:

text

Run Draft Approval on this page.

Use the source context first.

Review the draft for final approval.

Return the output with these fields:
- approved sections
- review needed sections
- blocked sections
- proof risks
- internal link risks
- schema cue risks
- readability risks
- blocked term risks
- approval decision
- next workflow route

Do not approve the draft if high-risk issues remain.

Route approved drafts into Draft Handoff.

Best for:

approved production drafts
client review
editorial review
rewrite approval
publish readiness

Output should include:

approved sections
review sections
blocked sections
risks
approval decision

Use this to:

Create the final gate before handoff.

Only approved drafts should move into schema cues, publishing, or monitoring.

54. Draft Handoff

Use this to move the finished draft downstream.

Short command:

text

Run Draft Handoff for this approved draft.

Expanded prompt:

text

Run Draft Handoff for this approved draft.

Use the source context first.

Route each approved draft item into the correct next workflow.

Return the output with these fields:
- page
- draft type
- final copy status
- internal link route
- information gain route
- SERP feature route
- schema cue route after approval
- publish route
- monitoring note
- revision notes
- blocked items
- handoff note

Do not leave approved copy without a next action.

Return a clean production handoff package.

Best for:

finished drafts
production handoff
publishing queues
SEO QA
post-approval workflows

Output should include:

page
draft type
final status
routes
handoff note

Use this to:

Move approved copy into final site operations.

Draft Handoff connects the finished page to internal links, SERP validation, schema cues, publishing, and monitoring.

Which Drafting or Rewriting Module Should You Run First?

Start with Draft Scope if the production boundary is unclear.

Start with Draft Goal if the task is vague.

Start with Draft Input Review if several files, briefs, URLs, or notes may feed production.

Start with Brief to Draft Alignment if an approved brief exists.

Start with Outline to Draft Alignment if an outline exists.

Start with First 100 Words Draft if the brief and outline are approved.

Start with Section Drafting if one section needs controlled production.

Start with Search Intent Rewrite if the page misses its approved query job.

Start with Semantic Drift Repair if the copy moves away from the approved purpose.

Start with Internal Link Rewrite if the page has weak link placement or anchor context.

Start with Draft QA if a full draft already exists.

Start with Draft Handoff if the page is approved and ready for downstream work.

Common Drafting and Rewriting Starting Points

I Have an Approved Brief

Start with Brief to Draft Alignment.

Prompt:

text

Run Brief to Draft Alignment for this brief.

Use the source context first.

Check that the approved brief is ready for production.

Return page title, brief goal, page role, user job, search intent, required sections, proof requirements, internal link requirements, blocked items, drafting risks, and next workflow route.

Do not draft if the brief lacks purpose, section requirements, proof rules, or link requirements.

Then run:

text

Run Outline to Draft Alignment for this outline.

Use the source context first.

Check that the outline matches the approved brief before drafting.

Return heading, heading purpose, required answer, proof need, internal link need, SERP target, overlap risk, missing section, section to remove, and next workflow route.

Do not draft from an outline that drifts from the brief.

Then run:

text

Draft this section from the approved brief.

Use the source context first.

Write only the requested section.

Return section heading, section draft, section purpose, user job served, required points covered, proof added, internal link added, revision note, and next workflow route.

Do not draft other sections.

Route the result into Drafting + Rewriting until the full page is complete.

I Have an Existing URL That Needs Rewriting

Start with Draft Scope.

Prompt:

text

Run Draft Scope for this page.

Use the source context first.

Define the production boundary before rewriting starts.

Return page or URL, rewrite type, approved inputs, source inputs to use, source inputs to ignore, page role, target user, allowed topics, blocked topics, and next workflow route.

Do not rewrite yet.

Then run:

text

Run Search Intent Rewrite on this page.

Use the source context first.

Rewrite the sections that fail the approved search intent.

Return current section, intent issue, revised section, answer added, format change, proof added, and next workflow route.

Do not change the page into a different intent target.

Then run:

text

Run Draft QA on this page.

Use the source context first.

Audit the draft before approval.

Return source context fit, page purpose fit, search intent fit, user job fit, section completeness, proof gaps, internal link gaps, anchor issues, snippet readiness, readability issues, blocked term issues, required fixes, and next workflow route.

Route the result into rewrite existing content or rewrite for search intent.

I Need to Fix Semantic Drift

Start with Semantic Drift Repair.

Prompt:

text

Run Semantic Drift Repair on this draft.

Use the source context first.

Find and repair copy that drifts from the page purpose, primary entity, user job, or approved brief.

Return drift section, drift type, source context issue, revised copy, removed copy, reason, and next workflow route.

Do not broaden the page.

Then run:

text

Run Page Purpose Lock for this draft.

Use the source context first.

Lock the draft to the approved page purpose.

Return page purpose, primary job, secondary support job, user need, page role, section risks, off-purpose content, required fix, and next workflow route.

Flag any section that does not serve the page purpose.

Then run:

text

Run Content Pruning on this draft.

Use the source context first.

Remove or move copy that weakens page focus.

Return content to remove, reason, better destination, revised passage, source context note, and next workflow route.

Do not remove copy that supports the page purpose.

Route the output into fix semantic drift.

I Need to Add Internal Links During a Rewrite

Start with Internal Link Placement Draft.

Prompt:

text

Draft internal link placements for this page.

Use the source context first.

Place required internal links inside relevant passages.

Return source passage, target page, link purpose, anchor direction, placement, user path served, page role supported, and next workflow route.

Do not add generic links.

Then run:

text

Draft anchor text for these internal links.

Use the source context first.

Write anchor text that matches the surrounding sentence and target page promise.

Return target page, anchor text, anchor intent, surrounding sentence, risk note, and next workflow route.

Avoid exact-match repetition.

Then run:

text

Run Internal Link Rewrite on this page.

Use the source context first.

Rewrite passages so internal links fit the user path and target page promise.

Return current passage, target page, anchor issue, revised passage, revised anchor, link purpose, and next workflow route.

Do not insert links without context.

Route the result into rewrite for internal links, semantic internal linking, or anchor text by intent.

I Need Snippet, FAQ, or PAA Blocks

Start with Snippet Block Draft.

Prompt:

text

Draft Snippet Blocks for this page.

Use the source context first.

Write extractable answer blocks that also help the reader.

Return snippet target, snippet type, block draft, target question, section placement, supporting detail, risk note, and next workflow route.

Use paragraph, ordered list, unordered list, definition, or table format only where it fits.

Then run:

text

Draft the FAQ Block for this page.

Use the source context first.

Write FAQs that support the page role and user path.

Return FAQ question, short answer, user state served, internal link need, schema cue eligibility after approval, risk note, and next workflow route.

Do not add filler FAQs.

Then run:

text

Draft PAA answers for this page.

Use the source context first.

Write short answers for the approved PAA questions.

Return PAA question, answer, answer format, section placement, internal link need, risk note, and next workflow route.

Keep each answer direct.

Route the result into SERP feature planning or Draft QA.

I Need to Rewrite a Docs Page

Start with Docs Rewrite.

Prompt:

text

Run Docs Rewrite on this page.

Use the source context first.

Rewrite documentation so the user can follow the task from input to output.

Return user task, rewritten intro, rewritten steps, inputs needed, output expected, support path, fallback path, and next workflow route.

Keep the page sequential.

Then run:

text

Run Support Section Rewrite on this support page.

Use the source context first.

Rewrite support copy so the user can complete the task.

Return support task, current issue, revised steps, missing input, expected output, fallback path, and next workflow route.

Keep the rewrite task-focused.

Then run:

text

Run Choppy Flow Repair on this draft.

Use the source context first.

Repair passage flow, transitions, section order, and sentence rhythm.

Return flow issue, affected passage, revised passage, transition added, section order note, and next workflow route.

Do not add filler transitions.

Route the result into Draft QA.

I Need Final Draft QA

Start with Draft QA.

Prompt:

text

Run Draft QA on this page.

Use the source context first.

Audit the draft before approval.

Return source context fit, page purpose fit, search intent fit, user job fit, section completeness, proof gaps, internal link gaps, anchor issues, snippet readiness, readability issues, blocked term issues, required fixes, and next workflow route.

Do not approve drafts with unresolved purpose, proof, link, readability, or blocked term issues.

Then run:

text

Run Draft Approval on this page.

Use the source context first.

Review the draft for final approval.

Return approved sections, review needed sections, blocked sections, proof risks, internal link risks, schema cue risks, readability risks, blocked term risks, approval decision, and next workflow route.

Do not approve the draft if high-risk issues remain.

Then run:

text

Run Draft Handoff for this approved draft.

Use the source context first.

Route each approved draft item into the correct next workflow.

Return page, draft type, final copy status, internal link route, information gain route, SERP feature route, schema cue route after approval, publish route, monitoring note, revision notes, blocked items, and handoff note.

Do not leave approved copy without a next action.

Route the approved draft into internal linking, SERP validation, schema cues after approval, publishing, or monitoring.

Output Review Checklist for Drafting and Rewriting

Before moving downstream, check the draft or rewrite for:

source context fit
approved brief fit
approved outline fit
page purpose fit
page role fit
search intent fit
user job fit
first 100 words
intro answer block
section completeness
heading clarity
definition block quality
process block quality
comparison block quality
table quality
FAQ quality
PAA answer quality
snippet block quality
summary box quality
examples
proof blocks
CTA timing
internal link placement
anchor text quality
approved entity context
semantic drift
repetition
choppy flow
thin sections
clutter
unsupported claims
readability
blocked terms
revision notes
approval status
downstream workflow routes

Do not move into publishing, schema cues, link implementation, or monitoring if purpose, proof, internal links, readability, blocked terms, approval status, or handoff route is unresolved.

How Drafting and Rewriting Connects to Other MIRENA Workflows

Drafting and Rewriting is the production layer.

It feeds other workflows but does not replace them.

An approved draft can feed semantic internal linking when final link paths need graph review.

A draft with weak differentiation can feed information gain work when the page needs useful additions.

A draft can feed Semantic SEO when meaning, coverage, and topic fit need review.

An entity-heavy draft can feed Entity SEO when entity structure, clarity, or salience needs deeper work.

A rewritten page can feed Content Briefs again if the rewrite exposes missing instructions.

Use MIRENA workflow when you need to decide the next route. Use MIRENA outputs when the finished draft package needs to follow a set handoff format.

Drafting and Rewriting Mistakes to Avoid

Mistake 1: Drafting Without Source Context

Do not draft from a keyword, title, competitor page, or old URL alone.

Source context tells MIRENA which topics, claims, links, proof points, and paths belong in the page.

Mistake 2: Drafting Before Brief Approval

Drafting should start after the brief is approved.

If page purpose, sections, proof, links, or blocked items are unclear, return to the brief workflow first.

Mistake 3: Treating Rewriting as Polishing

A rewrite is not only a copy polish.

It may need search intent repair, semantic drift repair, internal link repair, proof repair, structure repair, and CTA repair.

Mistake 4: Adding Internal Links Without Context

Internal links should fit the passage and user path.

Use Internal Link Placement Draft, Anchor Text Draft, and Internal Link Rewrite before approval.

Mistake 5: Chasing Snippets at the Reader’s Expense

Snippet blocks should help the page.

Do not add answer blocks, lists, or tables that make the page worse for users.

Mistake 6: Adding Proof After Claims Are Written

Proof should be part of the draft plan.

Use Proof Block Draft before approval, especially on product, service, comparison, and trust-heavy pages.

Mistake 7: Expanding Thin Content With Filler

Thin Content Expansion should add useful depth.

Do not pad the page with repeated ideas or broad background that does not support the user job.

Mistake 8: Approving Copy With Unresolved Risks

A draft is not ready if purpose, proof, links, readability, blocked terms, or schema cue risks remain unresolved.

Run Draft QA and Draft Approval before handoff.

FAQs About Drafting and Rewriting Workflow Prompts in MIRENA

What is a Drafting and Rewriting Workflow in MIRENA?

A Drafting and Rewriting Workflow turns approved instructions into page copy or repairs an existing page.

It covers section drafting, full rewrites, search intent repair, semantic drift repair, snippets, FAQs, tables, internal links, proof blocks, CTAs, readability, QA, approval, and handoff.

What should I run first?

Start with Draft Scope if the production boundary is unclear.

Start with Draft Goal if the task is vague.

Start with Brief to Draft Alignment if an approved brief exists.

Start with Outline to Draft Alignment if an approved outline exists.

Start with Draft QA if a finished draft already exists.

Is drafting the same as creating a content brief?

No.

A content brief defines instructions.

Drafting turns approved instructions into copy.

Can MIRENA rewrite an existing page?

Yes.

Use Draft Scope, Draft Goal, Draft Input Review, Search Intent Rewrite, Semantic Drift Repair, Structure Rewrite, Internal Link Rewrite, and Draft QA.

Can MIRENA rewrite only one section?

Yes.

Use Section Rewrite when one section is weak, unclear, or off-purpose.

Use Section Drafting when the section is approved but has not been written yet.

Can MIRENA fix search intent mismatch?

Yes.

Use Search Intent Lock to identify the mismatch, then use Search Intent Rewrite to repair the affected sections.

Can MIRENA fix semantic drift?

Yes.

Use Semantic Drift Repair to find and rewrite copy that moves away from the page purpose, primary entity, user job, or approved brief.

Use fix semantic drift when the existing page needs deeper drift repair.

Can MIRENA add internal links during rewriting?

Yes.

Use Internal Link Placement Draft, Anchor Text Draft, and Internal Link Rewrite.

Use semantic internal linking when the final route also needs architecture and entity support.

Can MIRENA write FAQ, PAA, and snippet blocks?

Yes.

Use FAQ Block Draft, PAA Answer Draft, Snippet Block Draft, FAQ Rewrite, PAA Rewrite, and Snippet Rewrite.

Schema cues should wait until after draft approval.

Can MIRENA create schema during drafting?

No.

MIRENA can prepare schema cue notes only after the draft is approved and only from visible approved content.

What should I do after a draft is approved?

Move the output into the correct next workflow.

Use semantic internal linking when final link paths need review.

Use information gain work when differentiation needs improvement.

Use SERP feature planning when snippet, FAQ, list, or table blocks need validation.

Use schema cues only after draft approval.

Use monitoring after publishing.