Move from instructions to controlled copy
Check the brief and outline before writing one approved block at a time.
- Brief to Draft Alignment
- Outline to Draft Alignment
- Section Drafting
- Draft QA
MIRENA docs · Production workflow
Choose the right MIRENA prompt for drafting, rewriting, QA, or handoff.
MIRENA drafting and rewriting workflow prompts are structured commands for turning an approved brief into copy or repairing an existing page. Each module states the job, required inputs, return fields, guardrails, and next route.
- Source context comes first
- Choose the smallest matching module
- Draft QA comes before approval
- Final schema follows approved copy
Prompt Router
Choose your starting state, job, and focus.
Recommended module
01 · Draft Scope
Run Draft Scope for [page, draft, block, files, or URL].
Common starting routes
Start from the material you already have.
The route changes when you have an approved brief, a live URL, one weak block, or a finished draft.
Diagnose the page before rewriting
Set the repair boundary, choose the primary issue, then check the completed draft.
- Draft Scope
- Intent, drift, or structure repair
- Link and proof repair
- Draft QA
Repair the smallest unit that fails
Keep working copy untouched outside the approved repair boundary.
- Choose intro, heading, block, FAQ, table, or snippet
- Run the matching repair
- Check local flow
- Run Draft QA
Check, approve, and hand off
Keep risk, blocked copy, link actions, and downstream routes visible.
- Draft QA
- Repair failed items
- Draft Approval
- Draft Handoff
Workflow map
Five phases hold the 54 modules together.
The rebuilt library keeps the full set, then lets each user enter at the phase that matches the work.
Set scope and readiness
Lock source context, page purpose, intent, user job, and approved inputs before copy starts.
Draft approved copy
Write approved openings, blocks, proof, links, and entity context from a checked brief and outline.
Repair and rewrite
Repair drift, intent, order, weak components, repetition, thin copy, and overlap.
Rewrite by page type
Apply page-specific rules to docs, use case, comparison, product, and service pages.
QA, approval, and handoff
Check the full draft, record approval, and route finished copy into the next workflow.
01 Draft Scope Define the production boundary before drafting or rewriting starts. Set scope and readiness
readinesssource contextapproval gate
Short command
Run Draft Scope for [page, draft, block, files, or URL].Expanded prompt
Run Draft Scope for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Name what should be written, repaired, held, or ignored. Record the page role, target user, approved inputs, and next route.
Return:
- target page, block, file, or URL
- approved source context
- current state
- finding or decision
- missing input or risk
- required action
- next workflow route
Do not draft yet. Flag missing approved inputs.
Route the result into Draft Goal or Draft Input Review.02 Draft Goal Choose one main production job and state how success will be reviewed. Set scope and readiness
readinesssource contextapproval gate
Short command
Run Draft Goal for [page, draft, block, files, or URL].Expanded prompt
Run Draft Goal for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Separate the primary production goal from secondary repair work. Record the completion test.
Return:
- target page, block, file, or URL
- approved source context
- current state
- finding or decision
- missing input or risk
- required action
- next workflow route
Do not combine several major goals in one pass.
Route the result into Draft Input Review or Brief to Draft Alignment.03 Draft Input Review Decide which files and notes may shape the draft. Set scope and readiness
readinesssource contextapproval gate
Short command
Run Draft Input Review for [page, draft, block, files, or URL].Expanded prompt
Run Draft Input Review for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Review each supplied file, URL, brief, outline, note, and proof asset. Mark it use, hold, ignore, or review.
Return:
- target page, block, file, or URL
- approved source context
- current state
- finding or decision
- missing input or risk
- required action
- next workflow route
Do not draft yet. Keep later QA inputs separate from production inputs.
Route the result into Source Context to Draft Fit or Brief to Draft Alignment.04 Source Context to Draft Fit Check that the proposed page or repair belongs inside the site and offer. Set scope and readiness
readinesssource contextapproval gate
Short command
Run Source Context to Draft Fit for [page, draft, block, files, or URL].Expanded prompt
Run Source Context to Draft Fit for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Compare the target with the site purpose, audience, offer, allowed topics, blocked topics, existing pages, and commercial route.
Return:
- target page, block, file, or URL
- approved source context
- current state
- finding or decision
- missing input or risk
- required action
- next workflow route
Do not write a page or block that fails source-context fit.
Route the result into Brief to Draft Alignment or Draft Approval.05 Brief to Draft Alignment Check that an approved brief contains enough instruction for production. Set scope and readiness
readinesssource contextapproval gate
Short command
Run Brief to Draft Alignment for [page, draft, block, files, or URL].Expanded prompt
Run Brief to Draft Alignment for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Check page purpose, page role, user job, required blocks, entities, proof, internal links, answer formats, and blocked items.
Return:
- target page, block, file, or URL
- approved source context
- current state
- finding or decision
- missing input or risk
- required action
- next workflow route
Do not draft from an incomplete or unapproved brief.
Route the result into Outline to Draft Alignment or First 100 Words Draft.06 Outline to Draft Alignment Check that the outline matches the approved brief before copy starts. Set scope and readiness
readinesssource contextapproval gate
Short command
Run Outline to Draft Alignment for [page, draft, block, files, or URL].Expanded prompt
Run Outline to Draft Alignment for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Review every heading for job, entity focus, answer form, proof, internal links, result format, and overlap.
Return:
- target page, block, file, or URL
- approved source context
- current state
- finding or decision
- missing input or risk
- required action
- next workflow route
Do not draft from an outline that moves away from the brief.
Route the result into Section Drafting or Heading Expansion.07 Page Purpose Lock Hold the page to one clear job. Set scope and readiness
readinesssource contextapproval gate
Short command
Run Page Purpose Lock for [page, draft, block, files, or URL].Expanded prompt
Run Page Purpose Lock for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
State the approved purpose and flag copy that does not explain, prove, support, compare, convert, or route that job.
Return:
- target page, block, file, or URL
- approved source context
- current state
- finding or decision
- missing input or risk
- required action
- next workflow route
Flag every block that does not serve the approved purpose.
Route the result into Section Drafting, Structure Rewrite, or Draft QA.08 Search Intent Lock Hold the draft to the approved query job and answer form. Set scope and readiness
readinesssource contextapproval gate
Short command
Run Search Intent Lock for [page, draft, block, files, or URL].Expanded prompt
Run Search Intent Lock for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Compare approved intent with the current page shape and mark every mismatch in depth, format, or action.
Return:
- target page, block, file, or URL
- approved source context
- current state
- finding or decision
- missing input or risk
- required action
- next workflow route
Do not turn the page into a different intent target.
Route the result into Section Drafting or Search Intent Rewrite.09 User Job Lock Define what the visitor must understand, decide, compare, or complete. Set scope and readiness
readinesssource contextapproval gate
Short command
Run User Job Lock for [page, draft, block, files, or URL].Expanded prompt
Run User Job Lock for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Tie the draft to one user job, one completion event, and the friction or trust need that blocks progress.
Return:
- target page, block, file, or URL
- approved source context
- current state
- finding or decision
- missing input or risk
- required action
- next workflow route
Do not add copy that makes the user job harder to complete.
Route the result into Page Role Draft Plan or Section Drafting.10 Page Role Draft Plan Make the copy act like the page role assigned in the site. Set scope and readiness
readinesssource contextapproval gate
Short command
Run Page Role Draft Plan for [page, draft, block, files, or URL].Expanded prompt
Run Page Role Draft Plan for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Translate the page role into copy behavior, proof order, link needs, CTA timing, and block priority.
Return:
- target page, block, file, or URL
- approved source context
- current state
- finding or decision
- missing input or risk
- required action
- next workflow route
Do not make a hub, support page, docs page, and conversion page read the same way.
Route the result into Section Drafting or Internal Link Placement Draft.11 First 100 Words Draft Write the first view so the page purpose and answer are clear. Draft approved copy
new copyapproved briefcomponent
Short command
Run First 100 Words Draft for [page, draft, block, files, or URL].Expanded prompt
Run First 100 Words Draft for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Write a direct opening that names the main entity, answers the page job, and signals the next useful block.
Return:
- target block and page job
- approved source inputs
- drafted copy
- entity and answer-form check
- proof or link added
- revision note
- next workflow route
Do not open with broad scene setting or an early product pitch.
Route the result into Intro Answer Block or Section Drafting.12 Intro Answer Block Write a concise answer block below the H1. Draft approved copy
new copyapproved briefcomponent
Short command
Run Intro Answer Block for [page, draft, block, files, or URL].Expanded prompt
Run Intro Answer Block for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Answer the core query in the first sentence, then add scope, conditions, or context without repeating it.
Return:
- target block and page job
- approved source inputs
- drafted copy
- entity and answer-form check
- proof or link added
- revision note
- next workflow route
Do not bury the answer or restate the H1 in softer wording.
Route the result into Section Drafting or Snippet Block Draft.13 Section Drafting Write one approved content block at a time. Draft approved copy
new copyapproved briefcomponent
Short command
Run Section Drafting for [page, draft, block, files, or URL].Expanded prompt
Run Section Drafting for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Write only the requested block from the approved brief and outline. Cover its assigned points, proof, and link needs.
Return:
- target block and page job
- approved source inputs
- drafted copy
- entity and answer-form check
- proof or link added
- revision note
- next workflow route
Do not draft unapproved blocks or widen the topic.
Route the result into The next approved block or Draft QA.14 Heading Expansion Turn an approved heading into a precise block instruction. Draft approved copy
new copyapproved briefcomponent
Short command
Run Heading Expansion for [page, draft, block, files, or URL].Expanded prompt
Run Heading Expansion for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Expand the heading only enough to state its job, entity focus, answer form, and boundary.
Return:
- target block and page job
- approved source inputs
- drafted copy
- entity and answer-form check
- proof or link added
- revision note
- next workflow route
Do not turn headings into long summaries or add a second intent.
Route the result into Section Drafting.15 Definition Block Draft Write a direct definition with clear boundaries. Draft approved copy
new copyapproved briefcomponent
Short command
Run Definition Block Draft for [page, draft, block, files, or URL].Expanded prompt
Run Definition Block Draft for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Define the term in the first sentence, name its defining attributes, and separate it from close alternatives.
Return:
- target block and page job
- approved source inputs
- drafted copy
- entity and answer-form check
- proof or link added
- revision note
- next workflow route
Do not pad the definition with history or broad background.
Route the result into Section Drafting or Draft QA.16 Process Block Draft Write a process users can follow from input to output. Draft approved copy
new copyapproved briefcomponent
Short command
Run Process Block Draft for [page, draft, block, files, or URL].Expanded prompt
Run Process Block Draft for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
State prerequisites, use ordered steps, mark decision points, and name the expected result and fallback.
Return:
- target block and page job
- approved source inputs
- drafted copy
- entity and answer-form check
- proof or link added
- revision note
- next workflow route
Do not hide missing inputs or present optional actions as required steps.
Route the result into Section Drafting or Draft QA.17 Comparison Block Draft Write a fair comparison around the buyer's real decision. Draft approved copy
new copyapproved briefcomponent
Short command
Run Comparison Block Draft for [page, draft, block, files, or URL].Expanded prompt
Run Comparison Block Draft for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Name the options, use stated criteria, show differences, and give a bounded decision rule.
Return:
- target block and page job
- approved source inputs
- drafted copy
- entity and answer-form check
- proof or link added
- revision note
- next workflow route
Do not claim one option wins without criteria and support.
Route the result into Table Block Draft or Draft QA.18 Table Block Draft Build a readable table that answers one question. Draft approved copy
new copyapproved briefcomponent
Short command
Run Table Block Draft for [page, draft, block, files, or URL].Expanded prompt
Run Table Block Draft for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Set a clear table purpose, label rows and columns, keep cells concise, and add a short interpretation below it.
Return:
- target block and page job
- approved source inputs
- drafted copy
- entity and answer-form check
- proof or link added
- revision note
- next workflow route
Do not use a table when prose or a short list is easier to understand.
Route the result into Section Drafting or Draft QA.19 FAQ Block Draft Write visible questions that remove a real objection or follow-up need. Draft approved copy
new copyapproved briefcomponent
Short command
Run FAQ Block Draft for [page, draft, block, files, or URL].Expanded prompt
Run FAQ Block Draft for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Use natural questions, answer directly, add only useful detail, and point to a deeper page when needed.
Return:
- target block and page job
- approved source inputs
- drafted copy
- entity and answer-form check
- proof or link added
- revision note
- next workflow route
Do not create filler questions or repeat headings already answered on the page.
Route the result into Draft QA or schema cue review after approval.20 PAA Answer Draft Write a concise answer for a related question. Draft approved copy
new copyapproved briefcomponent
Short command
Run PAA Answer Draft for [page, draft, block, files, or URL].Expanded prompt
Run PAA Answer Draft for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Answer in the first sentence and add one short support paragraph or list when needed.
Return:
- target block and page job
- approved source inputs
- drafted copy
- entity and answer-form check
- proof or link added
- revision note
- next workflow route
Do not make the answer depend on copy that appears far away.
Route the result into Draft QA.21 Snippet Block Draft Write a clean answer block for a paragraph, list, or table result. Draft approved copy
new copyapproved briefcomponent
Short command
Run Snippet Block Draft for [page, draft, block, files, or URL].Expanded prompt
Run Snippet Block Draft for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Match the answer form to the query and keep the main answer complete on its own.
Return:
- target block and page job
- approved source inputs
- drafted copy
- entity and answer-form check
- proof or link added
- revision note
- next workflow route
Do not remove needed context merely to make the block short.
Route the result into Draft QA or SERP Feature Planning.22 Summary Box Draft Write a compact recap for a decision or task. Draft approved copy
new copyapproved briefcomponent
Short command
Run Summary Box Draft for [page, draft, block, files, or URL].Expanded prompt
Run Summary Box Draft for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
State the main point, key conditions, and next action without repeating the full page.
Return:
- target block and page job
- approved source inputs
- drafted copy
- entity and answer-form check
- proof or link added
- revision note
- next workflow route
Do not use the box as a second introduction.
Route the result into Draft QA.23 Example Block Draft Show how the method or decision works in a concrete case. Draft approved copy
new copyapproved briefcomponent
Short command
Run Example Block Draft for [page, draft, block, files, or URL].Expanded prompt
Run Example Block Draft for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Name the starting condition, input, output, and lesson so the example supports the nearby claim.
Return:
- target block and page job
- approved source inputs
- drafted copy
- entity and answer-form check
- proof or link added
- revision note
- next workflow route
Do not present an invented example as a client result.
Route the result into Proof Block Draft or Draft QA.24 Proof Block Draft Connect a claim to the support needed before a user acts. Draft approved copy
new copyapproved briefcomponent
Short command
Run Proof Block Draft for [page, draft, block, files, or URL].Expanded prompt
Run Proof Block Draft for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
List each claim, identify its proof threshold, add approved evidence, and weaken or remove unsupported claims.
Return:
- target block and page job
- approved source inputs
- drafted copy
- entity and answer-form check
- proof or link added
- revision note
- next workflow route
Do not invent evidence, testimonials, metrics, or client outcomes.
Route the result into CTA Block Draft or Draft QA.25 CTA Block Draft Write the next action for the user's current readiness. Draft approved copy
new copyapproved briefcomponent
Short command
Run CTA Block Draft for [page, draft, block, files, or URL].Expanded prompt
Run CTA Block Draft for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Name the action, object, value, and fallback route after the page has supplied enough clarity and proof.
Return:
- target block and page job
- approved source inputs
- drafted copy
- entity and answer-form check
- proof or link added
- revision note
- next workflow route
Do not push a sale before the user has enough information to decide.
Route the result into Draft QA.26 Internal Link Placement Draft Place a link where it helps the reader take the next useful step. Draft approved copy
new copyapproved briefcomponent
Short command
Run Internal Link Placement Draft for [page, draft, block, files, or URL].Expanded prompt
Run Internal Link Placement Draft for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Rewrite the surrounding passage so the destination, reason to click, and page role are clear.
Return:
- target block and page job
- approved source inputs
- drafted copy
- entity and answer-form check
- proof or link added
- revision note
- next workflow route
Do not place links as a detached list when a contextual passage is available.
Route the result into Anchor Text Draft or Draft QA.27 Anchor Text Draft Write anchor variants that describe the destination and user action. Draft approved copy
new copyapproved briefcomponent
Short command
Run Anchor Text Draft for [page, draft, block, files, or URL].Expanded prompt
Run Anchor Text Draft for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Create concise anchors from the target entity, page role, and nearby sentence context.
Return:
- target block and page job
- approved source inputs
- drafted copy
- entity and answer-form check
- proof or link added
- revision note
- next workflow route
Do not use vague anchors or repeat the same exact match across every link.
Route the result into Internal Link Placement Draft or Draft QA.28 Entity Context Integration Add approved entities and relationships without creating an entity dump. Draft approved copy
new copyapproved briefcomponent
Short command
Run Entity Context Integration for [page, draft, block, files, or URL].Expanded prompt
Run Entity Context Integration for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Place the primary entity near defining attributes and add only supporting entities that clarify the block.
Return:
- target block and page job
- approved source inputs
- drafted copy
- entity and answer-form check
- proof or link added
- revision note
- next workflow route
Do not add an entity only because a competitor mentions it.
Route the result into Draft QA or Entity SEO review.29 Semantic Drift Repair Pull copy back to the approved purpose, entity, and user job. Repair and rewrite
existing copytargeted repairchange log
Short command
Run Semantic Drift Repair for [page, draft, block, files, or URL].Expanded prompt
Run Semantic Drift Repair for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Find passages that leave the source context or brief, then rewrite, move, or remove them.
Return:
- current copy and named issue
- approved page job
- revised copy
- copy moved or removed
- proof or link change
- reason for change
- next workflow route
Do not widen the page while repairing drift.
Route the result into Draft QA.30 Search Intent Rewrite Repair blocks that fail the approved query job. Repair and rewrite
existing copytargeted repairchange log
Short command
Run Search Intent Rewrite for [page, draft, block, files, or URL].Expanded prompt
Run Search Intent Rewrite for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Rewrite only passages that miss the intent, answer form, depth, or user decision.
Return:
- current copy and named issue
- approved page job
- revised copy
- copy moved or removed
- proof or link change
- reason for change
- next workflow route
Do not change the page into a different intent target.
Route the result into Draft QA.31 Structure Rewrite Repair block order and page shape before polishing sentences. Repair and rewrite
existing copytargeted repairchange log
Short command
Run Structure Rewrite for [page, draft, block, files, or URL].Expanded prompt
Run Structure Rewrite for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Reorder the page around answer, explanation, proof, decision support, and next action.
Return:
- current copy and named issue
- approved page job
- revised copy
- copy moved or removed
- proof or link change
- reason for change
- next workflow route
Do not keep weak order merely to preserve the old draft.
Route the result into Section Rewrite or Draft QA.32 Intro Rewrite Replace a slow or vague opening with a direct answer. Repair and rewrite
existing copytargeted repairchange log
Short command
Run Intro Rewrite for [page, draft, block, files, or URL].Expanded prompt
Run Intro Rewrite for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Rewrite the opening around page purpose, primary entity, user job, and a clear route into the body.
Return:
- current copy and named issue
- approved page job
- revised copy
- copy moved or removed
- proof or link change
- reason for change
- next workflow route
Do not open with generic scene setting or unsupported claims.
Route the result into Draft QA.33 Heading Rewrite Make headings state the job of each block. Repair and rewrite
existing copytargeted repairchange log
Short command
Run Heading Rewrite for [page, draft, block, files, or URL].Expanded prompt
Run Heading Rewrite for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Rewrite headings so they reflect intent, entity focus, answer form, and page order.
Return:
- current copy and named issue
- approved page job
- revised copy
- copy moved or removed
- proof or link change
- reason for change
- next workflow route
Do not force keywords into headings that no longer read naturally.
Route the result into Section Rewrite or Draft QA.34 Section Rewrite Repair one weak content block without rewriting the full page. Repair and rewrite
existing copytargeted repairchange log
Short command
Run Section Rewrite for [page, draft, block, files, or URL].Expanded prompt
Run Section Rewrite for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Keep the approved job, replace weak copy, and add proof or a contextual link only when required.
Return:
- current copy and named issue
- approved page job
- revised copy
- copy moved or removed
- proof or link change
- reason for change
- next workflow route
Do not rewrite unaffected blocks.
Route the result into Draft QA.35 FAQ Rewrite Repair weak, repetitive, or off-purpose FAQs. Repair and rewrite
existing copytargeted repairchange log
Short command
Run FAQ Rewrite for [page, draft, block, files, or URL].Expanded prompt
Run FAQ Rewrite for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Rewrite questions around real follow-up needs and give direct, bounded answers.
Return:
- current copy and named issue
- approved page job
- revised copy
- copy moved or removed
- proof or link change
- reason for change
- next workflow route
Do not add questions only to increase count.
Route the result into Draft QA or schema cue review after approval.36 Table Rewrite Repair table labels, criteria, cell content, and summary. Repair and rewrite
existing copytargeted repairchange log
Short command
Run Table Rewrite for [page, draft, block, files, or URL].Expanded prompt
Run Table Rewrite for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Make the table answer one question with readable labels, comparable cells, and a short interpretation.
Return:
- current copy and named issue
- approved page job
- revised copy
- copy moved or removed
- proof or link change
- reason for change
- next workflow route
Do not keep a table that is less clear than prose.
Route the result into Draft QA.37 Snippet Rewrite Repair a block that is vague, long, incomplete, or poorly formatted. Repair and rewrite
existing copytargeted repairchange log
Short command
Run Snippet Rewrite for [page, draft, block, files, or URL].Expanded prompt
Run Snippet Rewrite for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Rewrite the answer to match the query and result format without removing needed context.
Return:
- current copy and named issue
- approved page job
- revised copy
- copy moved or removed
- proof or link change
- reason for change
- next workflow route
Do not promise a result-feature placement.
Route the result into Draft QA or SERP Feature Planning.38 PAA Rewrite Repair a follow-up answer so it stands on its own. Repair and rewrite
existing copytargeted repairchange log
Short command
Run PAA Rewrite for [page, draft, block, files, or URL].Expanded prompt
Run PAA Rewrite for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Match the question intent, answer directly, add a scope note when needed, and remove repeated detail.
Return:
- current copy and named issue
- approved page job
- revised copy
- copy moved or removed
- proof or link change
- reason for change
- next workflow route
Do not copy the same answer across several related questions.
Route the result into Draft QA.39 Internal Link Rewrite Repair a link passage, destination, or anchor that does not help the user. Repair and rewrite
existing copytargeted repairchange log
Short command
Run Internal Link Rewrite for [page, draft, block, files, or URL].Expanded prompt
Run Internal Link Rewrite for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Rewrite the source passage so the destination page and reason to continue are clear.
Return:
- current copy and named issue
- approved page job
- revised copy
- copy moved or removed
- proof or link change
- reason for change
- next workflow route
Do not add links that interrupt the primary answer or send users backward.
Route the result into Draft QA or Semantic Internal Linking review.40 Conversion Path Rewrite Repair the route from useful content to the next action. Repair and rewrite
existing copytargeted repairchange log
Short command
Run Conversion Path Rewrite for [page, draft, block, files, or URL].Expanded prompt
Run Conversion Path Rewrite for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Place the CTA after enough explanation and proof, and give a lower-risk fallback path.
Return:
- current copy and named issue
- approved page job
- revised copy
- copy moved or removed
- proof or link change
- reason for change
- next workflow route
Do not push conversion before value and trust are present.
Route the result into Draft QA.41 Support Section Rewrite Repair support copy so the user can complete the task. Repair and rewrite
existing copytargeted repairchange log
Short command
Run Support Section Rewrite for [page, draft, block, files, or URL].Expanded prompt
Run Support Section Rewrite for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Rewrite the task as clear steps with required inputs, expected output, and a fallback path.
Return:
- current copy and named issue
- approved page job
- revised copy
- copy moved or removed
- proof or link change
- reason for change
- next workflow route
Keep the copy task-focused and do not hide failure states.
Route the result into Draft QA.42 Mixed Intent Rewrite Separate competing page jobs and keep one primary intent. Repair and rewrite
existing copytargeted repairchange log
Short command
Run Mixed Intent Rewrite for [page, draft, block, files, or URL].Expanded prompt
Run Mixed Intent Rewrite for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Name the intent conflict, retain the main job, and move or remove copy that belongs elsewhere.
Return:
- current copy and named issue
- approved page job
- revised copy
- copy moved or removed
- proof or link change
- reason for change
- next workflow route
Do not force separate search intents into one page when they need separate homes.
Route the result into Draft QA or topical map review.43 Repetition Repair Remove repeated claims, examples, phrases, and transitions while keeping needed entity support. Repair and rewrite
existing copytargeted repairchange log
Short command
Run Repetition Repair for [page, draft, block, files, or URL].Expanded prompt
Run Repetition Repair for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Find repetition, merge the strongest version, and record what was removed.
Return:
- current copy and named issue
- approved page job
- revised copy
- copy moved or removed
- proof or link change
- reason for change
- next workflow route
Keep necessary entity reinforcement. Remove lazy repetition.
Route the result into Draft QA.44 Choppy Flow Repair Connect passages and block order without adding filler transitions. Repair and rewrite
existing copytargeted repairchange log
Short command
Run Choppy Flow Repair for [page, draft, block, files, or URL].Expanded prompt
Run Choppy Flow Repair for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Repair abrupt jumps, sentence rhythm, and local order where the reader loses the thread.
Return:
- current copy and named issue
- approved page job
- revised copy
- copy moved or removed
- proof or link change
- reason for change
- next workflow route
Do not add empty transition phrases.
Route the result into Draft QA.45 Thin Content Expansion Add missing detail only where it helps the user and supports the brief. Repair and rewrite
existing copytargeted repairchange log
Short command
Run Thin Content Expansion for [page, draft, block, files, or URL].Expanded prompt
Run Thin Content Expansion for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Name the missing detail and add explanation, proof, example, or a useful route.
Return:
- current copy and named issue
- approved page job
- revised copy
- copy moved or removed
- proof or link change
- reason for change
- next workflow route
Do not add words only to make the page longer.
Route the result into Draft QA.46 Content Pruning Remove or move copy that weakens page focus. Repair and rewrite
existing copytargeted repairchange log
Short command
Run Content Pruning for [page, draft, block, files, or URL].Expanded prompt
Run Content Pruning for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Mark clutter, off-scope copy, and duplicate ideas, then state the better home or revised passage.
Return:
- current copy and named issue
- approved page job
- revised copy
- copy moved or removed
- proof or link change
- reason for change
- next workflow route
Do not cut useful depth that serves the approved page job.
Route the result into Draft QA.47 Consolidation Rewrite Merge overlapping pages or blocks into one canonical target. Repair and rewrite
existing copytargeted repairchange log
Short command
Run Consolidation Rewrite for [page, draft, block, files, or URL].Expanded prompt
Run Consolidation Rewrite for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Retain unique value, remove duplicate intent, and record redirects and internal-link updates.
Return:
- current copy and named issue
- approved page job
- revised copy
- copy moved or removed
- proof or link change
- reason for change
- next workflow route
Do not merge pages that serve separate user intent.
Route the result into Draft QA or Internal Linking.48 Docs Rewrite Rewrite documentation around a task from input to output. Rewrite by page type
page typerewriteuser path
Short command
Run Docs Rewrite for [page, draft, block, files, or URL].Expanded prompt
Run Docs Rewrite for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
State the user task, rewrite the order, name required inputs, show the expected result, and add support and fallback routes.
Return:
- page type and user job
- current issue
- rewritten copy or block order
- proof and trust changes
- internal-link and CTA changes
- revision note
- next workflow route
Keep the page sequential and do not hide prerequisites.
Route the result into Draft QA.49 Use Case Rewrite Rewrite a use case around the user problem, desired result, product fit, proof, and next path. Rewrite by page type
page typerewriteuser path
Short command
Run Use Case Rewrite for [page, draft, block, files, or URL].Expanded prompt
Run Use Case Rewrite for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Connect the problem to a specific workflow result, show fit and limits, and place proof before the CTA.
Return:
- page type and user job
- current issue
- rewritten copy or block order
- proof and trust changes
- internal-link and CTA changes
- revision note
- next workflow route
Do not turn the page into a generic product description.
Route the result into Draft QA.50 Comparison Rewrite Rewrite a comparison around stated criteria and a fair buyer decision. Rewrite by page type
page typerewriteuser path
Short command
Run Comparison Rewrite for [page, draft, block, files, or URL].Expanded prompt
Run Comparison Rewrite for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Name the buyer question, set criteria, rebuild the comparison table, and give a bounded verdict.
Return:
- page type and user job
- current issue
- rewritten copy or block order
- proof and trust changes
- internal-link and CTA changes
- revision note
- next workflow route
Do not use unsupported superiority claims or hide trade-offs.
Route the result into Draft QA.51 Product or Service Rewrite Rewrite offer copy around user fit, value, proof, objections, and action. Rewrite by page type
page typerewriteuser path
Short command
Run Product or Service Rewrite for [page, draft, block, files, or URL].Expanded prompt
Run Product or Service Rewrite for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Clarify the offer, who it is for, what it returns, what it does not promise, and the next action.
Return:
- page type and user job
- current issue
- rewritten copy or block order
- proof and trust changes
- internal-link and CTA changes
- revision note
- next workflow route
Do not add unsupported results, hidden terms, or a vague CTA.
Route the result into Draft QA.52 Draft QA Check the full draft before approval. QA, approval, and handoff
QAapprovalhandoff
Short command
Run Draft QA for [page, draft, block, files, or URL].Expanded prompt
Run Draft QA for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Review source-context fit, purpose, intent, user job, block completeness, proof, links, answer formats, readability, and blocked wording.
Return:
- review scope
- passed items
- review-needed items
- blocked items
- required repairs
- approval state
- next workflow route
Do not approve a draft with unresolved high-risk issues.
Route the result into Draft Approval or revision.53 Draft Approval Record which blocks pass, need review, or remain blocked. QA, approval, and handoff
QAapprovalhandoff
Short command
Run Draft Approval for [page, draft, block, files, or URL].Expanded prompt
Run Draft Approval for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
State the approval decision with any remaining proof, link, schema-cue, readability, or wording risk.
Return:
- review scope
- passed items
- review-needed items
- blocked items
- required repairs
- approval state
- next workflow route
Do not approve the draft while a high-risk issue remains.
Route the result into Draft Handoff.54 Draft Handoff Route approved copy into links, result-format review, schema cues, publishing, and monitoring. QA, approval, and handoff
QAapprovalhandoff
Short command
Run Draft Handoff for [page, draft, block, files, or URL].Expanded prompt
Run Draft Handoff for [page, draft, block, files, or URL].
Use the source context first.
Use only approved production inputs.
Build a clean handoff that names every downstream route and any item still held.
Return:
- review scope
- passed items
- review-needed items
- blocked items
- required repairs
- approval state
- next workflow route
Do not leave approved copy without a named next action.
Route the result into Internal Linking, SERP Feature Planning, schema cues, publishing, or monitoring.No module matches that search. Try a shorter task or clear the phase filter.
Prompt anatomy
A useful production prompt carries five controls.
A task name alone is not enough for high-risk or production-ready work.
Source context
Site, audience, offer, topic boundaries, existing pages, and workflow goal.
Approved input
Brief, outline, current copy, proof, links, or the precise block being repaired.
One job
Draft, repair, check, approve, or hand off. Large jobs are split into smaller passes.
Return contract
Named fields make the result easier to review, compare, and pass downstream.
Next route
The result names the next block, QA pass, approval gate, link review, or publish route.
Draft QA checkpoint
Check the draft before approval.
Use the checklist as a quick readiness test. It does not replace editorial, legal, technical, or subject review.
0 of 10 checks complete
Trust and limits
Keep sensitive input, claims, and approval states under human control.
Input responsibility
Do not submit personal, confidential, regulated, or sensitive material unless you have permission and the material is suitable for the service. Read the privacy policy and acceptable use policy.
Output responsibility
MIRENA output is working material. Review facts, proof, links, tone, commercial claims, and page behavior before publication or client delivery.
Schema boundary
Drafting may record schema cues. Final markup follows the approved visible page. Read the output documentation and legal disclaimer.
Questions before use
MIRENA drafting and rewriting prompt FAQ
What is the MIRENA drafting and rewriting prompt library?
It is a set of structured commands for turning an approved brief into copy or repairing an existing page. Each module names the task, required inputs, return fields, guardrails, and next workflow route.
Why does the library start with source context?
Source context tells MIRENA what the site is, who it serves, what it offers, which topics belong, which topics are blocked, which pages already exist, and where the finished page should route the user.
Which prompt should I run when I already have an approved brief?
Start with Brief to Draft Alignment. If an outline also exists, run Outline to Draft Alignment next. Then draft one approved block at a time and run Draft QA before approval.
Which prompt should I run for an existing URL?
Start with Draft Scope when the repair boundary is unclear. Then choose the smallest matching repair, such as Search Intent Rewrite, Semantic Drift Repair, Structure Rewrite, Internal Link Rewrite, or a page-type rewrite.
Can I rewrite only one block?
Yes. Use Intro Rewrite, Heading Rewrite, Section Rewrite, FAQ Rewrite, Table Rewrite, Snippet Rewrite, PAA Rewrite, or another component prompt that matches the weak block.
Why are there 54 modules when the old title said 51?
The current library contains 54 numbered modules. The rebuilt page removes the count from the H1 so later changes do not create a title and library mismatch.
Can MIRENA add internal links during a rewrite?
Yes. Internal Link Placement Draft, Anchor Text Draft, and Internal Link Rewrite cover placement, destination fit, surrounding copy, and anchor direction. A wider site link review may still be needed.
Can MIRENA create schema while drafting?
Drafting may record schema cues, but final markup should wait until the visible draft is approved. The structured data must describe the approved page rather than an earlier plan.
What should Draft QA check?
Draft QA should check source-context fit, page purpose, search intent, the user job, block completeness, proof, internal links, anchors, answer formats, readability, blocked wording, and the next workflow route.
What happens after Draft Approval?
Run Draft Handoff. The handoff routes approved copy into internal linking, information gain review, result-format review, schema cues, publishing, and monitoring while keeping blocked items visible.
Take the selected prompt into the live workflow.
Use source context, attach the approved material, run the smallest matching module, and keep the result moving into QA, approval, or handoff.