MIRENA docs · Briefing workflow
Choose the right MIRENA content brief prompt, build it, check it, and hand it off.
MIRENA content brief workflow prompts turn approved strategy and evidence into writer-ready page instructions. Each module defines one job, return fields, guardrails, and the next route.
Start with source context. The brief should define what the page must cover, prove, link to, format, avoid, and hand off before drafting begins.
- Source context comes first
- Choose the smallest matching module
- Brief QA comes before approval
- Final schema follows an approved written draft
Content Brief Prompt Router
Select the state, job, page type, and prompt depth.
The router creates prompt text in this browser tab. It does not submit or store the page, URL, file name, or brief text.
36 · New Page Brief
Turn an approved map item into a writer-ready brief for a new URL.
Common starting paths
Start from the material you already have.
Do not read every module before acting. Use the route that matches the current page state.
Create a new-page brief
Turn the approved page decision into blocks, proof, links, QA, approval, and handoff.
- 36 New Page
- 16 Blocks
- 22 Proof
- 25 Links
- 46-48 Gate
Plan a controlled rewrite
Record what stays, what changes, which links and proof need repair, and which constraints govern the rewrite.
- 37 Rewrite
- 25 Links
- 28 Constraints
- 46-48 Gate
Create a refresh brief
Protect working blocks while adding useful result-set, proof, link, and product updates.
- 38 Refresh
- 12 Gain
- 22 Proof
- 46-48 Gate
Build a task-led docs brief
Connect prerequisites, steps, inputs, outputs, support, fallback, components, and readability.
- 40 Docs
- 24 Components
- 31 Readability
- 46-48 Gate
Plan criteria, proof, and decision support
Set the buyer question, fair criteria, table job, evidence, differentiation, and next route.
- 42 Comparison
- 21 Table
- 22 Proof
- 12 Gain
- 46-48 Gate
Audit, approve, and route it
Find missing requirements, record the human decision, then assign every approved item to production.
- 46 QA
- 47 Approval
- 48 Handoff
Five controlled phases
The brief moves from page fit to production handoff.
Each phase reduces a different failure: wrong page, weak structure, unsupported instructions, wrong page type, or premature production.
Scope, fit, and intent
Set the page boundary, goal, evidence, role, audience, journey, intent, and answer form.
Browse this phase →Differentiation and page structure
Translate competitor evidence, user gain, topic limits, entities, sections, headings, answers, snippets, FAQs, and tables into writer instructions.
Browse this phase →Proof, UX, links, and writing controls
Record proof, reusable assets, interface components, links, CTA timing, language rules, sources, media, schema cues after approval, and exclusions.
Browse this phase →Page-type brief production
Create the correct brief for a new page, rewrite, refresh, consolidation, docs page, use case, comparison, offer, market, or multi-audience page.
Browse this phase →QA, approval, and handoff
Audit the brief, record the human decision, and route approved requirements downstream.
Browse this phase →Searchable prompt library
Browse all 48 content brief modules.
Search by job, return field, page type, or route. Open only the modules needed for the current brief.
Open the content brief template
48 modules shown
01 Brief Scope Define the boundary of the content brief before page instructions expand. Scope, fit, and intent
Short command
Run Brief Scope for [page, URL, files, or brief].Expanded prompt
Run Brief Scope for [page, URL, files, or brief].
Use the source context first.
Define the brief boundary, source inputs, allowed topic lanes, blocked topic lanes, page type, page role, and target audience.
Return the output with these fields:
- page or topic being briefed
- proposed URL
- page type
- page role
- target audience
- allowed topic lanes
- blocked topic lanes
- source inputs to use
- source inputs to ignore
- next workflow route
Do not draft the page.
Reject topics that do not fit the source context.
Flag missing inputs before the brief continues.
Route the output into Brief Goal, Brief Input Review.02 Brief Goal Choose the primary job the brief must achieve. Scope, fit, and intent
Short command
Run Brief Goal for [page, URL, files, or brief].Expanded prompt
Run Brief Goal for [page, URL, files, or brief].
Use the source context first.
Choose one primary brief goal and record success criteria, evidence, page role, page type, and drafting risks.
Return the output with these fields:
- primary brief goal
- secondary goals
- page role
- page type
- success criteria
- evidence needed
- risks before drafting
- next workflow route
Do not combine too many brief goals in one pass.
Do not draft the page.
Route the output into Brief Input Review, Page Purpose Brief.03 Brief Input Review Decide which files, URLs, exports, and earlier outputs may shape the brief. Scope, fit, and intent
Short command
Run Brief Input Review on [page, URL, files, or brief].Expanded prompt
Run Brief Input Review on [page, URL, files, or brief].
Use the source context first.
Review each input for source quality, brief value, risk, and whether it should be used, held, ignored, or reviewed.
Return the output with these fields:
- input name
- input type
- source quality
- brief value
- risk
- use, hold, ignore, or review
- reason
- missing input
- next workflow route
Do not create the brief yet.
Keep later-workflow material out of the brief when it does not belong.
Route the output into Source Context to Brief Fit, Page Purpose Brief.04 Source Context to Brief Fit Check that the proposed page belongs in the site, offer, audience, and topic space. Scope, fit, and intent
Short command
Run Source Context to Brief Fit for [page, URL, files, or brief].Expanded prompt
Run Source Context to Brief Fit for [page, URL, files, or brief].
Use the source context first.
Check source-context fit, audience fit, offer fit, topic fit, and the decision to keep, revise, merge, hold, or block the page.
Return the output with these fields:
- page or topic
- source context fit
- audience fit
- offer fit
- topic fit
- risk
- keep, revise, merge, hold, or block
- reason
- required source context update
- next workflow route
Do not brief a page that fails source-context fit.
Do not draft the page.
Route the output into Page Purpose Brief, Brief Approval.05 Page Purpose Brief Give the page one primary job before section instructions are created. Scope, fit, and intent
Short command
Run Page Purpose Brief for [page, URL, files, or brief].Expanded prompt
Run Page Purpose Brief for [page, URL, files, or brief].
Use the source context first.
Define the primary purpose, support purpose, user job, page role, conversion or support route, and success criteria.
Return the output with these fields:
- page title
- proposed URL
- primary purpose
- secondary support purpose
- user job
- page role
- conversion or support route
- success criteria
- next workflow route
Flag pages with too many jobs.
Do not draft the page.
Route the output into Page Role Brief, Audience and User Job Brief, Search Intent Brief.06 Page Role Brief Define how the page functions inside the wider site. Scope, fit, and intent
Short command
Run Page Role Brief for [page, URL, files, or brief].Expanded prompt
Run Page Role Brief for [page, URL, files, or brief].
Use the source context first.
Assign a page role and connect it to the parent page, support pages, siblings, link direction, and CTA route.
Return the output with these fields:
- page
- page role
- role reason
- parent page
- support pages
- sibling pages
- internal link direction
- CTA route
- next workflow route
Flag unclear or conflicting page roles.
Do not draft the page.
Route the output into Section Requirements Brief, Internal Link Requirements Brief.07 Audience and User Job Brief Define who the page serves and what the person needs to do. Scope, fit, and intent
Short command
Run Audience and User Job Brief for [page, URL, files, or brief].Expanded prompt
Run Audience and User Job Brief for [page, URL, files, or brief].
Use the source context first.
Record the target audience, user state, user job, main question, pain or need, knowledge level, desired outcome, and next step.
Return the output with these fields:
- target audience
- user state
- user job
- main question
- pain or need
- knowledge level
- desired outcome
- next step
- next workflow route
Flag audience groups that need separate pages or clearly separated blocks.
Do not draft the page.
Route the output into Journey Stage Brief, Search Intent Brief, UX Component Brief.08 Journey Stage Brief Set the page position in the user journey and the timing of proof, links, and CTAs. Scope, fit, and intent
Short command
Run Journey Stage Brief for [page, URL, files, or brief].Expanded prompt
Run Journey Stage Brief for [page, URL, files, or brief].
Use the source context first.
Define the journey stage, user state, proof need, comparison need, support need, CTA timing, and fallback path.
Return the output with these fields:
- journey stage
- user state
- stage reason
- proof need
- comparison need
- support need
- CTA timing
- fallback path
- next workflow route
Do not push conversion if the user needs proof, comparison, or support first.
Do not draft the page.
Route the output into CTA and Next Step Brief, Internal Link Requirements Brief.09 Search Intent Brief Define the search intent, page type, query class, and content treatment. Scope, fit, and intent
Short command
Run Search Intent Brief for [page, URL, files, or brief].Expanded prompt
Run Search Intent Brief for [page, URL, files, or brief].
Use the source context first.
Set the primary and secondary intent, query examples, user job, page type, content treatment, and SERP format notes.
Return the output with these fields:
- primary intent
- secondary intent
- query examples
- user job
- page type
- content treatment
- SERP format notes
- intent risks
- next workflow route
Flag mixed intent.
Do not force one page to satisfy conflicting intents.
Do not draft the page.
Route the output into SERP Format Brief, Section Requirements Brief.10 SERP Format Brief Choose answer formats that fit both the query and the reader. Scope, fit, and intent
Short command
Run SERP Format Brief for [page, URL, files, or brief].Expanded prompt
Run SERP Format Brief for [page, URL, files, or brief].
Use the source context first.
Plan paragraph, list, table, FAQ, comparison, and PAA formats before drafting.
Return the output with these fields:
- SERP target
- answer format
- paragraph snippet need
- ordered list need
- table need
- FAQ need
- comparison block need
- PAA angle
- risk note
- next workflow route
Do not add SERP blocks that weaken the page experience.
Do not draft the page.
Route the output into Snippet Target Brief, FAQ Brief, Table and Comparison Brief, SERP Feature Planning.11 Competitor Coverage Brief Use competitor and result-set evidence without copying structure or wording. Differentiation and page structure
Short command
Run Competitor Coverage Brief for [page, URL, files, or brief].Expanded prompt
Run Competitor Coverage Brief for [page, URL, files, or brief].
Use the source context first.
Separate common, overused, missing, and useful differentiating coverage, then record proof and format patterns.
Return the output with these fields:
- common coverage
- overused coverage
- missing coverage
- useful differentiation
- proof patterns
- format patterns
- sections to include
- sections to avoid
- next workflow route
Use competitor and SERP notes as evidence only.
Do not copy competitor structure or wording.
Route the output into Information Gain Brief, Section Requirements Brief.12 Information Gain Brief Define useful additions beyond repeated result-set coverage. Differentiation and page structure
Short command
Run Information Gain Brief for [page, URL, files, or brief].Expanded prompt
Run Information Gain Brief for [page, URL, files, or brief].
Use the source context first.
Record repeated coverage, weak existing coverage, a useful angle, an original example, proof, and the block where the gain belongs.
Return the output with these fields:
- repeated SERP coverage
- weak existing coverage
- unique angle
- useful addition
- original example
- proof need
- section placement
- risk note
- next workflow route
Do not add novelty that does not help the user.
Do not draft the page.
Route the output into Section Requirements Brief, Proof and Evidence Brief, Information Gain.13 User Gain Brief Define the practical task, decision, trust, and effort improvement the page must provide. Differentiation and page structure
Short command
Run User Gain Brief for [page, URL, files, or brief].Expanded prompt
Run User Gain Brief for [page, URL, files, or brief].
Use the source context first.
Record the user benefit, task helped, decision helped, effort reduced, trust supported, next step improved, and required page component.
Return the output with these fields:
- user benefit
- task helped
- decision helped
- effort reduced
- trust supported
- next step improved
- section requirement
- component requirement
- next workflow route
Flag blocks that are complete but not useful.
Do not draft the page.
Route the output into UX Component Brief, Section Requirements Brief, Drafting and Rewriting.14 Topic Coverage Brief Set the topics that belong, link out, move, or stay excluded. Differentiation and page structure
Short command
Run Topic Coverage Brief for [page, URL, files, or brief].Expanded prompt
Run Topic Coverage Brief for [page, URL, files, or brief].
Use the source context first.
Define required and supporting topics, parent and child topics, exclusions, move decisions, link-out topics, and overlap risk.
Return the output with these fields:
- required topic
- supporting topic
- topic to exclude
- topic to link out
- topic to move
- parent topic
- child topic
- overlap risk
- next workflow route
Do not turn the brief into a topical map.
Do not draft the page.
Route the output into Section Requirements Brief, Internal Link Requirements Brief.15 Entity Context Brief Turn approved entity notes into clear writer instructions without repeating an entity audit. Differentiation and page structure
Short command
Run Entity Context Brief for [page, URL, files, or brief].Expanded prompt
Run Entity Context Brief for [page, URL, files, or brief].
Use the source context first.
Record the primary entity, supporting entities, clarification needs, relationship notes, usage notes, block placement, and terms to avoid.
Return the output with these fields:
- primary entity
- supporting entities
- entity clarification need
- entity relationship note
- entity usage note
- section placement
- terms to avoid
- next workflow route
Do not run entity salience inside this brief.
Do not create final schema.
Use deeper entity work only when the approved notes are not enough.
Route the output into Section Requirements Brief, Drafting and Rewriting, Entity SEO and Salience.16 Section Requirements Brief Turn strategy into a clear block-by-block page plan. Differentiation and page structure
Short command
Run Section Requirements Brief for [page, URL, files, or brief].Expanded prompt
Run Section Requirements Brief for [page, URL, files, or brief].
Use the source context first.
Define every required block, its purpose, user job, intent, required points, proof, links, SERP target, and draft instruction.
Return the output with these fields:
- section name
- section purpose
- user job served
- intent served
- required points
- proof needed
- internal link need
- SERP target
- draft instruction
- next workflow route
Flag blocks that are not needed.
Do not draft the blocks.
Route the output into Heading Requirements Brief, Brief Approval.17 Heading Requirements Brief Give every heading a distinct job before drafting. Differentiation and page structure
Short command
Run Heading Requirements Brief for [page, URL, files, or brief].Expanded prompt
Run Heading Requirements Brief for [page, URL, files, or brief].
Use the source context first.
Define heading level, draft heading, purpose, block role, query or user job, required answer, links, and SERP target.
Return the output with these fields:
- heading level
- heading draft
- heading purpose
- section role
- target query or user job
- required answer
- internal link need
- SERP target
- next workflow route
Do not write long page copy.
Flag headings that overlap or drift.
Route the output into Article Outline, Drafting and Rewriting.18 Answer Target Brief Plan the direct answers that readers and retrieval systems need. Differentiation and page structure
Short command
Run Answer Target Brief for [page, URL, files, or brief].Expanded prompt
Run Answer Target Brief for [page, URL, files, or brief].
Use the source context first.
Define each answer target, question, format, placement, proof, link need, and risk.
Return the output with these fields:
- answer target
- question answered
- answer format
- ideal placement
- proof need
- internal link need
- risk note
- next workflow route
Keep answers clear, specific, and easy to extract.
Do not draft the full page.
Route the output into Snippet Target Brief, FAQ Brief, Drafting and Rewriting.19 Snippet Target Brief Plan paragraph, list, table, or definition blocks that also serve the on-page task. Differentiation and page structure
Short command
Run Snippet Target Brief for [page, URL, files, or brief].Expanded prompt
Run Snippet Target Brief for [page, URL, files, or brief].
Use the source context first.
Define the snippet target, type, question, answer-length guidance, placement, supporting detail, and risk.
Return the output with these fields:
- snippet target
- snippet type
- target question
- answer length guidance
- section placement
- supporting detail
- risk note
- next workflow route
Use a snippet format only where it fits the user need.
Do not draft the full page.
Route the output into Drafting and Rewriting, SERP Feature Planning.20 FAQ Brief Plan useful follow-up questions and answer requirements before writing. Differentiation and page structure
Short command
Run FAQ Brief for [page, URL, files, or brief].Expanded prompt
Run FAQ Brief for [page, URL, files, or brief].
Use the source context first.
Record each FAQ question, answer intent, user state, journey stage, answer requirement, link need, and later schema-cue eligibility.
Return the output with these fields:
- FAQ question
- answer intent
- user state
- journey stage
- answer requirement
- internal link need
- schema cue eligibility after approval
- risk note
- next workflow route
Do not add filler FAQs.
Do not create final schema before draft approval.
Route the output into Drafting and Rewriting, Schema Cues after approval.21 Table and Comparison Brief Plan a table, checklist, comparison, or decision block when it reduces effort. Differentiation and page structure
Short command
Run Table and Comparison Brief for [page, URL, files, or brief].Expanded prompt
Run Table and Comparison Brief for [page, URL, files, or brief].
Use the source context first.
Define the block type, criteria, rows, columns, source evidence, proof requirement, and placement.
Return the output with these fields:
- block type
- comparison need
- criteria
- rows
- columns
- source evidence
- proof requirement
- placement
- next workflow route
Do not create a table if prose is clearer.
Do not draft the full page.
Route the output into Drafting and Rewriting, Information Gain.22 Proof and Evidence Brief Tell the writer what support is required before a claim is written. Proof, UX, links, and writing controls
Short command
Run Proof and Evidence Brief for [page, URL, files, or brief].Expanded prompt
Run Proof and Evidence Brief for [page, URL, files, or brief].
Use the source context first.
Map claims and blocks to evidence, methodology, data, screenshots, reviews, policy notes, author notes, examples, and missing proof.
Return the output with these fields:
- claim or section
- proof needed
- evidence source
- evidence gap
- placement
- risk if missing
- next workflow route
Flag unsupported claims.
Remove, revise, or hold a claim when proof is missing.
Route the output into Drafting and Rewriting, Information Gain, Brief Approval.23 Example and Template Brief Plan practical assets that help the user complete the page task. Proof, UX, links, and writing controls
Short command
Run Example and Template Brief for [page, URL, files, or brief].Expanded prompt
Run Example and Template Brief for [page, URL, files, or brief].
Use the source context first.
Plan examples, templates, prompt blocks, checklists, mini workflows, or copyable assets with placement and source needs.
Return the output with these fields:
- asset type
- user job served
- placement
- required content
- proof or source need
- internal link need
- lead value
- next workflow route
Do not add assets that distract from the page role.
Do not draft the full page.
Route the output into Drafting and Rewriting, Content Briefs.24 UX Component Brief Plan components that reduce effort, clarify choices, support trust, or guide the next step. Proof, UX, links, and writing controls
Short command
Run UX Component Brief for [page, URL, files, or brief].Expanded prompt
Run UX Component Brief for [page, URL, files, or brief].
Use the source context first.
Choose the component type, purpose, placement, user state, friction reduced, proof supported, and draft instruction.
Return the output with these fields:
- component type
- purpose
- placement
- user state served
- friction reduced
- proof supported
- draft instruction
- next workflow route
Every component must have one clear job.
Do not add decorative components that compete with the page task.
Route the output into Drafting and Rewriting.25 Internal Link Requirements Brief Make required internal links part of the brief rather than a late cleanup task. Proof, UX, links, and writing controls
Short command
Run Internal Link Requirements Brief for [page, URL, files, or brief].Expanded prompt
Run Internal Link Requirements Brief for [page, URL, files, or brief].
Use the source context first.
Define source page, target page, link purpose, page role, user path, anchor direction, placement, and priority.
Return the output with these fields:
- source page
- target page
- link purpose
- page role supported
- user path supported
- anchor direction
- placement
- priority
- next workflow route
Do not add generic links.
Do not add links that break the primary task block.
Route the output into Anchor Instruction Brief, Drafting and Rewriting, Semantic Internal Linking.26 Anchor Instruction Brief Define truthful, varied anchor direction for required internal links. Proof, UX, links, and writing controls
Short command
Run Anchor Instruction Brief for [page, URL, files, or brief].Expanded prompt
Run Anchor Instruction Brief for [page, URL, files, or brief].
Use the source context first.
Set the target page, anchor intent, recommended direction, surrounding passage, placement, user state, and risk.
Return the output with these fields:
- target page
- anchor intent
- recommended anchor direction
- surrounding passage
- placement
- user state served
- risk note
- next workflow route
Do not overpromise or misdescribe the target.
Do not force exact-match repetition.
Route the output into Drafting and Rewriting.27 CTA and Next Step Brief Define the useful next action, fallback path, and timing. Proof, UX, links, and writing controls
Short command
Run CTA and Next Step Brief for [page, URL, files, or brief].Expanded prompt
Run CTA and Next Step Brief for [page, URL, files, or brief].
Use the source context first.
Set the primary next step, fallback path, CTA purpose, placement, user readiness, trust need, and support need.
Return the output with these fields:
- primary next step
- fallback path
- CTA purpose
- CTA placement
- user readiness
- trust need before CTA
- support need before CTA
- risk note
- next workflow route
Do not push conversion before the user has enough clarity and trust.
Do not draft the full page.
Route the output into Drafting and Rewriting, Behavioral Mapping.28 Drafting Constraints Brief Set inclusions, exclusions, order, proof, links, and format boundaries before drafting. Proof, UX, links, and writing controls
Short command
Run Drafting Constraints Brief for [page, URL, files, or brief].Expanded prompt
Run Drafting Constraints Brief for [page, URL, files, or brief].
Use the source context first.
Define required inclusions and exclusions, block-order rules, tone, style, prohibited claims, proof, links, and formatting.
Return the output with these fields:
- required inclusions
- required exclusions
- section order rules
- tone rules
- style rules
- prohibited claims
- proof requirements
- internal link rules
- formatting rules
- next workflow route
Do not draft the page.
Hold unresolved constraints before production.
Route the output into Drafting and Rewriting.29 Tone and Style Brief Define voice, pacing, reading level, example style, and wording boundaries. Proof, UX, links, and writing controls
Short command
Run Tone and Style Brief for [page, URL, files, or brief].Expanded prompt
Run Tone and Style Brief for [page, URL, files, or brief].
Use the source context first.
Set tone, voice, reading level, sentence style, example style, preferred words, avoided words, and risk.
Return the output with these fields:
- tone
- voice
- reading level
- sentence style
- example style
- words to use
- words to avoid
- risk note
- next workflow route
Keep the tone clear, useful, and direct.
Do not draft the page.
Route the output into Drafting and Rewriting.30 Lexicon and Blocked Terms Brief Create vocabulary controls before the writer begins. Proof, UX, links, and writing controls
Short command
Run Lexicon and Blocked Terms Brief for [page, URL, files, or brief].Expanded prompt
Run Lexicon and Blocked Terms Brief for [page, URL, files, or brief].
Use the source context first.
Record preferred terms, limited terms, blocked terms, replacements, repetition risk, phrase risk, and block guidance.
Return the output with these fields:
- preferred terms
- terms to limit
- blocked terms
- replacement terms
- phrase risk
- repetition risk
- section guidance
- next workflow route
Apply the project blocked-word list.
Do not draft the page.
Route the output into Drafting and Rewriting, Brief Approval.31 Readability Brief Set parsing and reading requirements without removing needed depth. Proof, UX, links, and writing controls
Short command
Run Readability Brief for [page, URL, files, or brief].Expanded prompt
Run Readability Brief for [page, URL, files, or brief].
Use the source context first.
Define reading level, sentence and paragraph rules, lists, tables, summaries, complexity risks, and route.
Return the output with these fields:
- reading level
- sentence guidance
- paragraph guidance
- list guidance
- table guidance
- summary needs
- complexity risks
- next workflow route
Keep paragraphs clear and scannable.
Do not draft the page.
Route the output into Drafting and Rewriting.32 Source and Citation Brief Define evidence and citation rules before claims appear. Proof, UX, links, and writing controls
Short command
Run Source and Citation Brief for [page, URL, files, or brief].Expanded prompt
Run Source and Citation Brief for [page, URL, files, or brief].
Use the source context first.
Map claim types to source priority, internal sources, external sources, citation notes, and proof gaps.
Return the output with these fields:
- claim type
- source needed
- source priority
- internal source
- external source
- citation note
- proof gap
- next workflow route
Flag claims that need evidence before drafting.
Do not invent a source.
Route the output into Drafting and Rewriting, Brief Approval.33 Visual and Media Brief Plan visuals that clarify, prove, compare, or help a task. Proof, UX, links, and writing controls
Short command
Run Visual and Media Brief for [page, URL, files, or brief].Expanded prompt
Run Visual and Media Brief for [page, URL, files, or brief].
Use the source context first.
Define the visual type, job, placement, user need, source, alt-text direction, production note, and route.
Return the output with these fields:
- visual type
- purpose
- placement
- user need served
- source needed
- alt text direction
- production note
- next workflow route
Do not add visuals that do not help the user.
Do not place decorative media before the primary task.
Route the output into Drafting and Rewriting, Design Handoff.34 Schema Cue Brief Record schema candidates from visible, approved copy after the draft is approved. Proof, UX, links, and writing controls
Short command
Run Schema Cue Brief for [page, URL, files, or brief].Expanded prompt
Run Schema Cue Brief for [page, URL, files, or brief].
Use the source context first.
Review the approved draft and record candidate types, supported visible content, required fields, unsupported fields, readiness, and risk.
Return the output with these fields:
- schema type candidate
- supported visible content
- required field
- unsupported field
- risk note
- schema readiness
- next workflow route
Run this only after human approval of the written draft.
Do not create final schema before draft approval.
Do not use hidden or unsupported content.
Route the output into Schema Cues after approval, Compliance Review.35 Do Not Include Brief Define exclusions that prevent drift, overreach, and duplicate content. Proof, UX, links, and writing controls
Short command
Run Do Not Include Brief for [page, URL, files, or brief].Expanded prompt
Run Do Not Include Brief for [page, URL, files, or brief].
Use the source context first.
Record excluded topics, claims, links, CTAs, comparisons, reasons, and better destinations.
Return the output with these fields:
- excluded topic
- excluded claim
- excluded link
- excluded CTA
- excluded comparison
- reason
- better destination if any
- next workflow route
Move off-role material to a better page.
Do not draft excluded material.
Route the output into Brief Approval, Drafting and Rewriting.36 New Page Brief Turn an approved map item into a writer-ready brief for a new URL. Page-type brief production
Short command
Run New Page Brief for [page, URL, files, or brief].Expanded prompt
Run New Page Brief for [page, URL, files, or brief].
Use the source context first.
Create a full brief from the approved map item, source context, page role, user job, intent, proof, links, formats, and constraints.
Return the output with these fields:
- page title
- URL
- page role
- target user
- user job
- search intent
- required sections
- proof requirements
- internal link requirements
- SERP targets
- information gain requirements
- tone rules
- blocked items
- next workflow route
Do not draft the page.
Use an approved map item or record the missing approval.
Route the output into Brief QA, Drafting and Rewriting.37 Rewrite Brief Create repair instructions for an existing URL before rewriting. Page-type brief production
Short command
Run Rewrite Brief for [page, URL, files, or brief].Expanded prompt
Run Rewrite Brief for [page, URL, files, or brief].
Use the source context first.
Record current and target roles, rewrite goal, protected blocks, revisions, removals, missing blocks, link fixes, proof fixes, and CTA fixes.
Return the output with these fields:
- current URL
- current page role
- target page role
- rewrite goal
- sections to keep
- sections to revise
- sections to remove
- missing sections
- internal link fixes
- proof fixes
- CTA fixes
- next workflow route
Do not rewrite the page yet.
Protect blocks that still perform their job.
Route the output into Drafting and Rewriting.38 Refresh Brief Plan an update around performance, search, content, link, result-set, and business signals. Page-type brief production
Short command
Run Refresh Brief for [page, URL, files, or brief].Expanded prompt
Run Refresh Brief for [page, URL, files, or brief].
Use the source context first.
Record the refresh reason, content to keep, update, or remove, new blocks, link updates, information gain, proof updates, and route.
Return the output with these fields:
- page
- refresh reason
- content to keep
- content to update
- content to remove
- new sections needed
- internal link updates
- information gain need
- proof updates
- next workflow route
Do not rewrite the page yet.
Protect working content unless evidence supports a change.
Route the output into Drafting and Rewriting, Information Gain.39 Consolidation Brief Plan a merge without losing distinct intent or useful content. Page-type brief production
Short command
Run Consolidation Brief for [page, URL, files, or brief].Expanded prompt
Run Consolidation Brief for [page, URL, files, or brief].
Use the source context first.
Choose the canonical target, merge reason, content to keep or remove, blocks to combine, redirect note, link update, proof gap, and route.
Return the output with these fields:
- source pages
- canonical target
- merge reason
- content to keep
- content to remove
- sections to combine
- redirect note
- internal link update
- proof gap
- next workflow route
Do not merge content that serves separate intent.
Do not perform the merge during briefing.
Route the output into Drafting and Rewriting, Internal Linking.40 Docs Brief Create a task-led brief for documentation, onboarding, or support. Page-type brief production
Short command
Run Docs Brief for [page, URL, files, or brief].Expanded prompt
Run Docs Brief for [page, URL, files, or brief].
Use the source context first.
Define the docs title, user task, prerequisite knowledge, steps, inputs, outputs, support path, fallback, links, and route.
Return the output with these fields:
- docs page title
- user task
- prerequisite knowledge
- steps needed
- inputs needed
- outputs expected
- support path
- fallback path
- internal link requirements
- next workflow route
Keep the brief task-focused.
Do not draft the page.
Route the output into Drafting and Rewriting.41 Use Case Brief Tie a page to one real user job, problem, outcome, and product fit. Page-type brief production
Short command
Run Use Case Brief for [page, URL, files, or brief].Expanded prompt
Run Use Case Brief for [page, URL, files, or brief].
Use the source context first.
Record the use case, user job, audience, problem, desired outcome, product fit, proof, support pages, conversion route, and next route.
Return the output with these fields:
- use case
- user job
- audience
- problem
- desired outcome
- product fit
- proof needed
- support pages
- conversion route
- next workflow route
Do not make the use case generic.
Do not draft the page.
Route the output into Drafting and Rewriting, Proof and Evidence Brief.42 Comparison Brief Create a fair comparison around a buyer question and stated criteria. Page-type brief production
Short command
Run Comparison Brief for [page, URL, files, or brief].Expanded prompt
Run Comparison Brief for [page, URL, files, or brief].
Use the source context first.
Define options, buyer question, comparison criteria, table requirements, proof, differentiation, conversion route, and next route.
Return the output with these fields:
- comparison topic
- options compared
- buyer question
- comparison criteria
- table requirements
- proof requirements
- differentiation need
- conversion route
- next workflow route
Do not create a comparison page without clear buyer value.
Do not draft the page.
Route the output into Drafting and Rewriting, Information Gain.43 Product or Service Brief Connect the offer, audience, problem, benefits, proof, objections, and action route. Page-type brief production
Short command
Run Product or Service Brief for [page, URL, files, or brief].Expanded prompt
Run Product or Service Brief for [page, URL, files, or brief].
Use the source context first.
Define the offer, audience, problem solved, core benefits, proof, objections, comparison needs, CTA route, and support links.
Return the output with these fields:
- offer
- target audience
- problem solved
- core benefits
- proof requirements
- objections
- comparison needs
- CTA route
- support links
- next workflow route
Flag claims that need evidence.
Do not draft the page.
Route the output into Drafting and Rewriting, Proof and Evidence Brief.44 Local or Market Brief Adapt a page to a place, market, or segment without producing thin local copy. Page-type brief production
Short command
Run Local or Market Brief for [page, URL, files, or brief].Expanded prompt
Run Local or Market Brief for [page, URL, files, or brief].
Use the source context first.
Record location or market, audience, local need, offer fit, proof, trust cues, links, exclusions, and route.
Return the output with these fields:
- market or location
- audience
- local need
- service fit
- proof needed
- local trust cues
- internal link requirements
- content to avoid
- next workflow route
Do not add unsupported local claims.
Do not draft the page.
Route the output into Drafting and Rewriting, Proof and Evidence Brief.45 Multi Audience Brief Serve more than one audience while keeping one primary page job. Page-type brief production
Short command
Run Multi Audience Brief for [page, URL, files, or brief].Expanded prompt
Run Multi Audience Brief for [page, URL, files, or brief].
Use the source context first.
Define the primary and secondary audience, shared user job, audience-specific block needs, exclusions, link route, split-page risk, and route.
Return the output with these fields:
- primary audience
- secondary audience
- shared user job
- audience-specific section need
- section to avoid
- internal link route
- split page risk
- next workflow route
Flag cases where separate pages are needed.
Do not draft the page.
Route the output into Section Requirements Brief, Brief Approval.46 Brief QA Find missing purpose, evidence, links, requirements, and risk before approval. QA, approval, and handoff
Short command
Run Brief QA on [page, URL, files, or brief].Expanded prompt
Run Brief QA on [page, URL, files, or brief].
Use the source context first.
Audit source context, page purpose, intent, block requirements, proof, links, information gain, blocked terms, schema risk, approval status, and required fixes.
Return the output with these fields:
- missing source context
- unclear page purpose
- unclear intent
- weak section requirement
- missing proof
- missing internal link
- missing information gain
- blocked term risk
- schema risk
- approval status
- required fix
- next workflow route
Do not approve briefs with missing purpose, weak evidence, unclear block rules, or unresolved risks.
Route the output into Brief Approval, Revision.47 Brief Approval Record the human gate before drafting or rewriting starts. QA, approval, and handoff
Short command
Run Brief Approval on [page, URL, files, or brief].Expanded prompt
Run Brief Approval on [page, URL, files, or brief].
Use the source context first.
Review approved, review-needed, blocked, and missing items, then record drafting, link, proof, and later schema-cue risks.
Return the output with these fields:
- approved items
- review needed items
- blocked items
- missing inputs
- drafting risks
- link risks
- proof risks
- schema cue risks
- approval decision
- next workflow route
Do not approve the brief without source-context fit, page purpose, block requirements, proof, and link requirements.
Route the output into Drafting and Rewriting.48 Brief Handoff Route every approved brief requirement into the correct production workflow. QA, approval, and handoff
Short command
Run Brief Handoff for [page, URL, files, or brief].Expanded prompt
Run Brief Handoff for [page, URL, files, or brief].
Use the source context first.
Create a clean handoff that assigns drafting, rewriting, links, information gain, SERP formatting, later schema cues, owners, blocked items, and notes.
Return the output with these fields:
- page
- brief goal
- drafting route
- rewrite route
- internal link route
- information gain route
- SERP feature route
- schema cue route after approval
- blocked items
- owner note
- handoff note
Use this only for an approved brief.
Do not leave an approved requirement without a next action.
Route the output into Drafting and Rewriting, Internal Linking, Information Gain, SERP Feature Planning, Schema Cue Review after draft approval.Writer-ready brief anatomy
A strong brief is a page operating plan, not a keyword sheet.
The final packet should tell the writer what to produce and tell the reviewer how to check it.
Page identity
Title, URL, type, role, parent, purpose, and conversion or support route.
User and intent
Audience, user state, journey stage, job, question, primary intent, and fallback path.
Topic and entities
Required topics, excluded topics, primary entity, supporting entities, relationships, and terms to avoid.
Block requirements
Every required block, its job, required points, answer target, proof, links, and format.
Gain and evidence
Repeated coverage, useful additions, original examples, claims, approved sources, and proof gaps.
Links and next paths
Target URL, link purpose, anchor direction, placement, CTA timing, and fallback route.
Writing controls
Tone, reading level, blocked terms, prohibited claims, order rules, media, and exclusions.
QA and handoff
Blocking issues, approval decision, owners, production routes, and later schema-cue route.
Brief QA gate
Do not send a weak brief into drafting.
Use the checklist to find missing context, purpose, structure, proof, links, language controls, and approval state.
Brief QA finds the problem. Brief Approval records the human decision. Brief Handoff assigns the approved work.
Workflow boundaries
Briefing sits between approved planning and page production.
The page should make the boundary visible so a user does not run drafting, final linking, or structured data too early.
What belongs before the brief
- Source context and project guardrails
- Approved page or map decision
- Evidence intake and source-quality decisions
- User-path, entity, result-set, link, proof, or performance notes when available
What belongs after approval
- Drafting or rewriting
- Internal link production
- Information gain work
- SERP block production and final schema cues from approved visible copy
Input and privacy boundary
Do not paste passwords, full payment-card details, restricted client material, or sensitive personal data without a lawful and approved reason. The router itself does not submit or store its form values.
Output and claim boundary
MIRENA output is working material. Human review remains required for facts, sources, claims, links, code, accessibility, legal duties, and publication.
No ranking, traffic, lead, sale, revenue, or rich-result outcome is promised.
Common questions
Content brief workflow FAQ
What is the MIRENA Content Brief Workflow Prompt Library?
It is a 48-module set of structured commands for turning approved strategy and evidence into writer-ready page instructions. Each module names one briefing job, return fields, guardrails, and the next route.
Why does source context come first?
Source context defines the site, audience, offer, allowed topics, blocked topics, page role, proof routes, internal link rules, and workflow boundary. Without it, a brief can be polished and still belong to the wrong page or site.
Which content brief module should I run first?
Start with Brief Scope when the page boundary is unclear, Brief Input Review when several files may shape the brief, a page-type module when the job is already known, or Brief QA when a draft brief already exists.
Is a content brief the same as a draft?
No. A brief tells the writer what the page must do, cover, prove, link to, avoid, and hand off. Drafting begins only after the brief passes QA and receives human approval.
Can I build a brief from one keyword?
A keyword can be evidence, but it is not enough by itself. Add source context, page role, audience, user job, intent, site routes, and the strongest available proof or result-set notes before creating writer instructions.
Do I need to run all 48 modules?
No. Choose the smallest module that fits the current job. A full page brief may use several modules, but each run should have one clear purpose and a stated next route.
Can the workflow plan internal links and anchors?
Yes. Internal Link Requirements Brief records the target, purpose, placement, page role, and user path. Anchor Instruction Brief records truthful anchor direction and the surrounding passage.
Can the workflow create schema markup?
No final markup should be created during briefing. Schema Cue Brief runs only after a human approves the written draft and may use only visible, supported copy.
What happens after Brief Approval?
Brief Handoff routes approved requirements into drafting, rewriting, internal linking, information gain, SERP formatting, and later schema-cue review. Blocked or unresolved items stay outside production.
Does a MIRENA content brief guarantee rankings or traffic?
No. The workflow improves control, clarity, evidence, and handoff quality. Search performance still depends on competition, authority, technical quality, implementation, links, user response, and later maintenance.
Turn an approved page decision into a controlled writing packet.
Build the prompt, attach the strongest evidence, run Brief QA, record the approval decision, and hand the approved requirements to the correct production lane.