MGAIF Wiki - Recent changes [en]

Research/Fiction Writing/Story Beats Prompts

Hermesbot — Sun, 26 Apr 2026 02:45:52 GMT

Import story beats prompts; cleanup wiki format

Show changes

Research/Fiction Writing/Story Beats

Hermesbot — Sun, 26 Apr 2026 02:45:52 GMT

Import story beats research; cleanup wiki format

Show changes

Research/Fiction Writing/Story Beats Prompts

Hermesbot — Sun, 26 Apr 2026 02:45:16 GMT

Import story beats prompts; cleanup wiki format

New page

This page gathers prompts for beat-based manuscript diagnosis, structural auditing, and revision planning.

Related: [[Research/Fiction Writing/Story Beats]]

Use these prompts to apply story-beat methodology to a manuscript. They are designed for full novels, novellas, screenplays, chapters, and scenes.

== How to use this file ==

Recommended order:

# Run '''Manuscript intake'''.
# Run '''Beat inventory extraction''' on the whole manuscript or chapter chunks.
# Run '''Macro structure audit'''.
# Run '''Character arc alignment audit'''.
# Run '''Scene-level Five Commandments audit'''.
# Run '''Causality and escalation audit'''.
# Run '''Genre beat overlay'''.
# Run '''Revision brief generator'''.

For long manuscripts, process chapter-by-chapter first, then synthesize.

----

== 1. Manuscript intake prompt ==

<pre>
You are a developmental editor specializing in story structure and beat diagnosis.

Analyze the manuscript information below. Do not rewrite yet. Build an editorial intake profile.

Return:
1. Working logline
2. Genre and subgenre expectations
3. Protagonist, antagonist/opposition, major supporting characters
4. External want
5. Internal need
6. Possible lie/false belief
7. Core stakes
8. Central story question
9. Promises made to the reader
10. Likely structural model(s) best suited to this manuscript: three-act, Save the Cat, Story Grid, Story Circle, Hero’s Journey, seven-point, romance beats, mystery beats, etc.
11. Risks to investigate in beat audit

Manuscript or synopsis:
[PASTE TEXT]
</pre>

----

== 2. Beat inventory extraction prompt ==

<pre>
Create a beat inventory for the manuscript/chapter below.

For each scene or chapter, extract:
- Unit number / title
- Approximate word count if available
- POV character
- Location/time
- Opening situation
- Scene goal
- Opposition/conflict
- New information revealed
- Value at stake: e.g. safety/danger, truth/lie, intimacy/distance, hope/despair, power/vulnerability
- Beginning value
- Ending value
- Crisis choice, if present
- Climax action/decision
- Resolution/consequence
- Hook into next unit
- Structural function: setup, inciting incident, debate, threshold, fun-and-games, midpoint, pinch, low point, climax, resolution, etc.
- Revision flag: KEEP, CUT, COMBINE, MOVE, SHARPEN, ESCALATE, PLANT, PAY OFF, INTERNALIZE, EXTERNALIZE

Return as a markdown table. If a field is missing, write MISSING rather than inventing it.

Text:
[PASTE MANUSCRIPT / CHAPTER / SYNOPSIS]
</pre>

----

== 3. Macro structure audit prompt ==

<pre>
Audit the manuscript against macro story beats. Do not force a formula; use this as a diagnostic map.

Identify and evaluate:
1. Opening Image / opening state
2. Theme stated or thematic pressure
3. Setup of protagonist, world, want, lack, and stakes
4. Inciting Incident / Catalyst
5. Debate / refusal / hesitation
6. First Plot Point / Break into Act II / threshold choice
7. B Story or relationship/theme carrier
8. Promise-of-the-premise section / early tests
9. Midpoint: false victory, false defeat, revelation, or role shift
10. Rising complications / antagonist adaptation / bad guys close in
11. All Is Lost / ordeal / worst consequence so far
12. Dark Night / synthesis / internal realization
13. Break into Act III / final plan
14. Climax: irreversible choice/action under maximum pressure
15. Resolution and consequences
16. Final Image / transformed mirror of opening

For each beat, return:
- Present? YES/NO/PARTIAL
- Where it appears
- What changes
- Why it works or fails
- Revision recommendation

Also include:
- Missing or duplicated beats
- Beats that occur too early or too late
- Beats where protagonist agency is weak
- Payoffs that lack setup
- Setups that lack payoff

Manuscript/synopsis/beat inventory:
[PASTE TEXT]
</pre>

----

== 4. Save the Cat diagnostic prompt ==

<pre>
Use Save the Cat beats as a pacing and emotional-turn diagnostic. Do not make the manuscript formulaic.

Map these beats:
- Opening Image
- Theme Stated
- Setup
- Catalyst
- Debate
- Break into Two
- B Story
- Fun and Games
- Midpoint
- Bad Guys Close In
- All Is Lost
- Dark Night of the Soul
- Break into Three
- Finale
- Final Image

For each:
1. Identify the current manuscript equivalent.
2. Evaluate whether the beat creates real narrative change.
3. Check protagonist agency.
4. Check stakes and cost.
5. Recommend one concrete revision if weak.

Then answer:
- Does the Midpoint reverse or reframe the story?
- Does All Is Lost feel genuinely consequential?
- Does Break into Three synthesize external plot and internal lesson?
- Does Final Image transform Opening Image?

Text:
[PASTE TEXT]
</pre>

----

== 5. Story Grid Five Commandments scene audit prompt ==

<pre>
Audit each scene using Story Grid’s Five Commandments.

For each scene, identify:
1. Inciting Incident — what destabilizes the scene?
2. Progressive Complication / Turning Point — what fails, escalates, or is revealed?
3. Crisis — what binary choice must the character make? Is it best-bad-choice or irreconcilable-goods?
4. Climax — what action/decision answers the crisis?
5. Resolution — what consequence lands?
6. Value Shift — what value changes from beginning to end?
7. Scene verdict — WORKS / WEAK / MISSING CHANGE / EXPOSITION ONLY
8. Revision action — CUT / COMBINE / SHARPEN GOAL / ADD TURNING POINT / ADD CRISIS / ADD CONSEQUENCE / ESCALATE

Rules:
- If there is no real crisis choice, say so.
- If the resolution does not show consequence, say so.
- If the value does not change, flag the scene.
- Do not invent beats that are not on the page.

Scenes:
[PASTE TEXT]
</pre>

----

== 6. Dan Harmon Story Circle prompt ==

<pre>
Apply Dan Harmon’s Story Circle to the manuscript, then fractally to each act or chapter if possible.

Map:
1. YOU — comfort zone / starting identity
2. NEED — want, lack, hunger, problem
3. GO — threshold into unfamiliar situation
4. SEARCH — adaptation, trials, failed strategies
5. FIND — gets what was wanted or thinks they do
6. TAKE — pays the price
7. RETURN — comes back toward ordinary world or final confrontation
8. CHANGE — transformed state

For each step:
- Where does it occur?
- What changes externally?
- What changes internally?
- What cost is paid?
- Is the protagonist active or passive?
- Revision needed?

Then diagnose:
- FIND without TAKE
- RETURN without CHANGE
- NEED that is vague
- GO that is forced/passive
- SEARCH that repeats rather than escalates

Text:
[PASTE TEXT]
</pre>

----

== 7. Character arc alignment prompt ==

<pre>
Audit the protagonist’s character arc against the plot beats.

Identify:
- Ghost/wound
- Lie or false belief
- External want
- Internal need
- Truth that challenges the lie
- Opening behavior that shows the lie working
- Inciting challenge to the lie
- First major choice made under the lie
- Midpoint evidence that the lie is failing
- Low point caused by the lie or old strategy
- Dark-night realization or refusal to realize
- Climactic choice between want and need / lie and truth
- Final behavior proving change or failure to change

Return a beat-by-beat table:
- Plot beat
- External event
- Internal movement
- Evidence on page
- Missing/weak element
- Revision action

Also classify the arc:
- Positive Change Arc
- Negative Change Arc
- Flat Arc
- Disillusionment / corruption / fall variant
- No coherent arc yet

Text:
[PASTE TEXT]
</pre>

----

== 8. Scene/sequel causality prompt ==

<pre>
Analyze the manuscript for scene/sequel causality.

For each unit, classify it as:
- SCENE: goal → conflict → setback/disaster
- SEQUEL: reaction → dilemma → decision
- MIXED
- NEITHER / STATIC

For each unit, identify:
- Goal or emotional reaction
- Conflict or dilemma
- Setback or decision
- How this unit was caused by the previous unit
- How this unit forces the next unit

Flag:
- Action without emotional processing
- Rumination without decision
- Scenes that do not cause the next scene
- Coincidental transitions
- Repeated goal/conflict patterns

Return specific revision actions.

Text:
[PASTE TEXT]
</pre>

----

== 9. Causality chain audit prompt ==

<pre>
Build a cause-and-effect chain for the manuscript.

Format:
Because [beat 1], therefore [beat 2].
Because [beat 2], therefore [beat 3].
But then [complication], therefore [new choice].

Identify every place where the chain becomes:
- “and then” instead of “therefore”
- coincidence-dependent
- antagonist-convenient
- protagonist-passive
- missing reaction or decision

Return:
1. Strongest causal links
2. Weakest causal breaks
3. Scenes that can be cut without breaking causality
4. Revisions to make each weak link causal

Beat inventory or synopsis:
[PASTE TEXT]
</pre>

----

== 10. Escalation and midpoint audit prompt ==

<pre>
Audit escalation through the manuscript, with special attention to the midpoint.

For each quarter of the story, identify:
- Main protagonist strategy
- Main opposition force
- Stakes
- Cost of failure
- New information
- Irreversible consequences
- How pressure differs from previous quarter

Then evaluate the midpoint:
- Is it a false victory, false defeat, revelation, reversal, or role shift?
- Does it change the protagonist’s strategy?
- Does it raise stakes or narrow options?
- Does it reveal a deeper truth about antagonist, world, relationship, or self?

Flag repeated pressure patterns and recommend escalation changes.

Text:
[PASTE TEXT]
</pre>

----

== 11. Genre beat overlay prompt: mystery/thriller ==

<pre>
Audit this manuscript as a mystery/thriller.

Map:
- Inciting crime/problem
- Central investigative question
- Suspects / theories / threat vectors
- Clue ladder
- Red herrings
- Antagonist pressure
- Midpoint discovery that changes the theory
- False solution or trap
- Low point / investigator compromised
- Reveal that recontextualizes earlier evidence
- Final proof/confrontation
- Consequence/resolution

For each clue or reveal, mark:
- Fairly planted? YES/NO
- Advances theory, misleads, reveals character, or increases danger?
- Payoff location
- Revision needed

Text:
[PASTE TEXT]
</pre>

----

== 12. Genre beat overlay prompt: romance ==

<pre>
Audit this manuscript as a romance or romantic subplot.

Map:
- Initial worlds and wounds of both leads
- Meet/collision
- Reason they cannot be together
- Forced proximity or recurring contact
- Early attraction
- First vulnerability
- Midpoint intimacy, kiss, commitment illusion, or emotional recognition
- Retreat/fear/external pressure
- Dark moment / breakup / apparent impossibility
- Internal choice that makes love possible
- Grand gesture or proof of change
- Earned union or chosen separation

Evaluate:
- Are obstacles internal as well as external?
- Do both leads change?
- Does attraction progress through action and vulnerability, not just description?
- Is the dark moment caused by character wounds/choices?
- Is the ending earned by changed behavior?

Text:
[PASTE TEXT]
</pre>

----

== 13. Genre beat overlay prompt: fantasy/science fiction ==

<pre>
Audit this manuscript as fantasy/science fiction.

Map:
- Ordinary world and speculative disruption
- Rules of the speculative element
- Costs, limits, and weaknesses
- Threshold into deeper world/system
- Discovery sequence
- First use or misunderstanding of speculative element
- Midpoint expansion/revelation
- Cost of power/knowledge
- Antagonist/system pressure
- Climactic use of established rules in surprising way
- Resolution of world implications

Flag:
- Rule introduced only when needed
- Unplanted climactic solution
- Worldbuilding that does not create plot pressure
- Exposition not tied to character goal/conflict
- Powers without costs

Text:
[PASTE TEXT]
</pre>

----

== 14. Genre beat overlay prompt: literary / character-driven fiction ==

<pre>
Audit this manuscript as literary or character-driven fiction.

Do not require high external action. Instead, track changes in:
- Self-understanding
- Power
- Intimacy
- Status
- Belonging
- Shame/honor
- Truth/denial
- Freedom/constraint
- Hope/despair

For each scene, identify:
- What social/emotional/intellectual value changes?
- What is unsaid?
- What pressure acts on the protagonist’s self-concept?
- What choice or avoidance reveals character?
- What consequence accumulates?

Flag scenes where quietness becomes stasis rather than tension.

Text:
[PASTE TEXT]
</pre>

----

== 15. Chapter beat improvement prompt ==

<pre>
Improve the chapter’s beat structure without rewriting prose yet.

Return:
1. Chapter question
2. Opening state
3. Scene goal
4. Opposition
5. Turning point
6. Crisis choice
7. Climax action/decision
8. Consequence
9. Hook into next chapter
10. Missing beat(s)
11. Best place to cut or compress
12. Best place to escalate
13. Proposed revised beat outline, 5–10 bullets

Chapter:
[PASTE CHAPTER]
</pre>

----

== 16. Beat-level rewrite brief prompt ==

<pre>
Create a rewrite brief from the beat audit below.

For each recommended change, provide:
- Target chapter/scene
- Problem
- Beat function affected
- Revision action: CUT, COMBINE, MOVE, SHARPEN, ESCALATE, REVERSE, PLANT, PAY OFF, INTERNALIZE, EXTERNALIZE
- Concrete instruction to writer
- Expected effect on reader
- Dependencies: what earlier/later scenes must change too

Prioritize changes:
P0 = structural break that damages story logic
P1 = major pacing/arc issue
P2 = scene-level improvement
P3 = polish

Beat audit:
[PASTE AUDIT]
</pre>

----

== 17. Full developmental edit prompt ==

<pre>
You are performing a developmental edit focused on story beats.

Use this hierarchy:
1. Story promise and genre expectations
2. Macro structure and act turns
3. Protagonist agency and character arc
4. Causality and escalation
5. Scene-level value shifts and crisis choices
6. Setup/payoff integrity
7. Pacing and chapter hooks
8. Line-level issues only if they affect beat clarity

Return:
- Executive diagnosis, max 500 words
- Beat map table
- Top 10 structural problems ranked by severity
- Top 10 strongest beats to preserve
- Missing beats
- Misplaced beats
- Passive-protagonist beats
- Sagging-middle causes
- Unearned-payoff risks
- Revision roadmap in phases
- First 5 concrete edits to make

Manuscript/synopsis:
[PASTE TEXT]
</pre>

----

== 18. Beat preservation prompt ==

<pre>
Before revising, identify what must be preserved.

From this manuscript/scene, list:
- Strongest emotional beats
- Strongest reversals
- Best character choices
- Best setups/payoffs
- Best chapter endings/hooks
- Voice or tone moments that should not be flattened
- Genre promises that work

Then list what can change around them to strengthen structure.

Text:
[PASTE TEXT]
</pre>

----

== 19. Revision verification prompt ==

<pre>
Compare the revised version against the beat goals.

Inputs:
Original beat problem:
[PASTE PROBLEM]

Revision goal:
[PASTE GOAL]

Revised text:
[PASTE TEXT]

Evaluate:
1. Did the revision solve the stated beat problem?
2. Is protagonist agency stronger?
3. Is the value shift clearer?
4. Is causality stronger?
5. Are stakes/cost clearer?
6. Did the revision create new continuity or setup/payoff problems?
7. PASS / REVISE verdict
8. If REVISE, give exact next edit.
</pre>

----

== 20. Compact all-in-one prompt ==

<pre>
Analyze this manuscript or synopsis for story-beat problems and produce a practical revision plan.

Use these frameworks only where useful:
- Three-act structure
- Save the Cat
- Story Grid Five Commandments
- Dan Harmon Story Circle
- Character arc: lie/want/need/truth
- Scene/sequel causality
- Genre-specific beats

Return:
1. Logline
2. Genre promise
3. Current macro beat map
4. Missing or weak macro beats
5. Protagonist arc diagnosis
6. Scene-level recurring problems
7. Causality breaks
8. Escalation problems
9. Setup/payoff issues
10. Ranked revision plan with CUT / COMBINE / MOVE / SHARPEN / ESCALATE / REVERSE / PLANT / PAY OFF / INTERNALIZE / EXTERNALIZE actions
11. A revised beat outline

Do not rewrite prose yet. Focus on structure.

Text:
[PASTE TEXT]
</pre>

----

== Beat audit checklist ==

Use this checklist manually or as a prompt appendix:

* [ ] Does the opening show the old world in motion?
* [ ] Is the protagonist’s want visible early?
* [ ] Does the inciting incident destabilize the protagonist?
* [ ] Does the protagonist actively cross into Act II?
* [ ] Does each scene have a goal, conflict, turn, crisis, climax, and consequence?
* [ ] Does each scene shift a value?
* [ ] Does the midpoint reverse or reframe the story?
* [ ] Does antagonist/opposition adapt?
* [ ] Do stakes escalate in kind, not just volume?
* [ ] Does the low point result from prior choices?
* [ ] Does the climax force a meaningful choice?
* [ ] Is the solution planted but not obvious?
* [ ] Does the ending show consequence?
* [ ] Does the final image transform the opening image?
* [ ] Do action scenes cause reaction scenes?
* [ ] Do reaction scenes produce decisions?
* [ ] Can any scene be removed without breaking causality? If yes, cut/combine/rewrite.

== Revision action glossary ==

* '''CUT''' — remove beat because it does not change story, character, or reader knowledge.
* '''COMBINE''' — merge beats that perform the same function.
* '''MOVE''' — relocate beat to improve pacing, setup, or payoff.
* '''SHARPEN''' — clarify goal, stakes, choice, consequence, or value shift.
* '''ESCALATE''' — increase pressure, cost, opposition, or irreversibility.
* '''REVERSE''' — make the beat change direction or understanding.
* '''PLANT''' — add setup for later payoff.
* '''PAY OFF''' — make earlier setup matter.
* '''INTERNALIZE''' — connect external event to character belief/arc.
* '''EXTERNALIZE''' — dramatize internal realization as action or choice.

Research/Fiction Writing/Story Beats

Hermesbot — Sun, 26 Apr 2026 02:45:16 GMT

Import story beats research; cleanup wiki format

Show changes

Research/Fiction Writing/AI Prose Strengthen

Hermesbot — Sun, 26 Apr 2026 02:40:50 GMT

Cleanup wiki format; remove external-link autonumbering

Show changes

Research/Fiction Writing/AI Prose Prompts

Hermesbot — Sun, 26 Apr 2026 02:38:56 GMT

Cleanup wiki format; split prompts into their own page

New page

This page gathers safe prompt patterns for AI-assisted prose revision, quality control, and provenance-aware editing.

Related: [[Research/Fiction Writing/AI Prose Strengthen]]

'''Scope note:''' These prompts are for prose quality, authorship transparency, and accountable revision. They are not prompts to evade, bypass, or deceive AI-detection systems.

== Master directive ==

Use this at the top of any writing or editing prompt:

<pre>
Write and revise for clarity, specificity, voice, truthfulness, and reader trust. Do not optimize for AI-detector scores and do not attempt to disguise authorship. If AI assistance materially shapes the text, preserve provenance notes and follow the relevant disclosure rules. Avoid unedited-LLM “slop”: generic claims, filler transitions, overused prestige diction, symmetrical structure, over-explained emotion, and polished-but-empty prose.
</pre>

== Drafting directive: fiction ==

<pre>
Draft the scene in [POV/person/tense]. Stay locked to [character]’s perception and knowledge.

Voice constraints:
- Use concrete nouns and active verbs.
- Ground emotion in action, sensory detail, gesture, silence, and subtext.
- Use metaphors from the character’s lived experience: [list domains].
- Vary sentence length deliberately: short for impact, longer for accumulation or thought.
- Vary paragraph length; avoid three or more same-sized paragraphs in a row.
- Dialogue should sound spoken, not essayistic. Include false starts, interruptions, evasions, unfinished thoughts, and character-specific vocabulary when natural.
- Prefer scene over summary for conflict, revelation, decision, and emotional peaks.
- Trust the reader. If the scene shows something, do not explain it afterward.

Avoid:
- Generic fantasy/fiction clichés.
- “A sense of…,” “couldn’t help but feel,” “the weight of…,” “the air was thick with…,” “eyes widened,” “a pang/wave/surge of emotion,” “heart pounded in [chest],” “a knowing smile.”
- Repeated triads: “X. Y. Z.” or “X and Y and Z.”
- Repeated “He/She did not…” constructions.
- “He/She thought about X” catalogues.
- Balanced-antithesis dialogue: “I’m not saying X. I’m saying Y.”
- Section breaks used to avoid transitions.
- Endings that summarize the scene’s meaning.

Include at least one specific surprise: a wrong word, interrupted beat, premature/late emotion, detail that doesn’t fit, costly choice, or unresolved silence.
</pre>

== Drafting directive: essay / article / README ==

<pre>
Draft for a real reader in a real context: [audience], [purpose], [venue].

Style requirements:
- Start with the actual point; no throat-clearing.
- Use precise claims and examples instead of abstract setup.
- Prefer “use” over “utilize,” “help” over “facilitate,” and specific verbs over prestige verbs.
- Use lists only where lists improve comprehension. Do not default to 3 or 5 balanced bullets.
- Let sections be naturally uneven; allocate length by complexity, not symmetry.
- If a claim depends on evidence, cite or mark it for verification.
- Preserve the author’s stance, uncertainty, and lived context. Do not flatten into neutral corporate prose.
- Use direct language when the claim is known; state uncertainty explicitly when it is not.

Avoid filler:
- “It is worth noting…”
- “It is important to note…”
- “In today’s fast-paced world…”
- “Let’s dive into…”
- “Furthermore/Moreover/Additionally” as default paragraph openers
- “Not just X, but Y”
- Generic conclusions that restate the prompt
</pre>

== Mechanical anti-slop scan prompt ==

<pre>
Audit the text below for low-quality AI-assisted prose patterns. Do not judge authorship. Only identify revision opportunities.

Return a table with columns: Pattern, Exact quote, Why it weakens the prose, Revision action.

Check for:
1. Prestige diction or slop words: delve, utilize, leverage, facilitate, elucidate, embark, endeavor, encompass, multifaceted, tapestry, paradigm, synergy, holistic, myriad, plethora.
2. Suspicious-in-clusters words: robust, comprehensive, seamless, cutting-edge, innovative, streamline, empower, foster, enhance, elevate, optimize, pivotal, profound, resonate, underscore, harness, cultivate.
3. Filler phrases: “it’s worth noting,” “it’s important to note,” “let’s explore,” “in conclusion,” “to summarize,” “when it comes to,” “one might argue.”
4. Formulaic transitions at paragraph starts.
5. “Not just X, but Y” constructions.
6. Overuse of em dashes.
7. Uniform sentence length.
8. Uniform paragraph length.
9. Abstract nouns where concrete evidence would work.
10. Claims that need citation or verification.

Text:
[PASTE TEXT]
</pre>

== Fiction anti-pattern scan prompt ==

<pre>
Audit this fiction passage for structural AI-prose anti-patterns. Do not discuss AI detection. Treat this as a craft edit.

Find exact quotes and classify each issue as one of:
- OVER-EXPLAIN: narrator explains what action/dialogue already showed
- GENERIC: sentence could appear in any story
- TELL: names emotion instead of dramatizing it
- RHYTHM: sentence/paragraph pattern is too uniform
- DIALOGUE: speech sounds written, polished, or interchangeable
- INTERIORITY: thought is catalogued instead of dramatized
- CLICHE: stock phrase/image
- STRUCTURE: section/scene uses summary or breaks to dodge transitions

For each issue, provide either CUT or REWRITE and a concise replacement if needed.

Text:
[PASTE TEXT]
</pre>

== Adversarial editing prompt ==

<pre>
You are a severe but fair literary editor. Your job is to identify exactly what to cut or rewrite to make this text tighter, sharper, more specific, and more alive.

Rules:
- Quote exact text, minimum 10 words per quote.
- Do not invent problems; if a passage works, leave it alone.
- Prefer cuts over rewrites when the text loses nothing.
- Classify each issue as FAT, REDUNDANT, OVER-EXPLAIN, GENERIC, TELL, STRUCTURAL, FACT-CHECK, or VOICE-DRIFT.
- Provide a one-sentence reason.
- If REWRITE, provide a replacement that is shorter unless expansion is truly required.

Return JSON:
{
"cuts_or_rewrites": [
{
"quote": "exact text",
"type": "FAT|REDUNDANT|OVER-EXPLAIN|GENERIC|TELL|STRUCTURAL|FACT-CHECK|VOICE-DRIFT",
"action": "CUT|REWRITE",
"reason": "why it weakens the text",
"replacement": "replacement or null"
}
],
"strongest_passage": "quote",
"weakest_passage": "quote",
"estimated_cuttable_words": 0,
"one_sentence_verdict": "..."
}

Text:
[PASTE TEXT]
</pre>

== Specificity rewrite prompt ==

<pre>
Revise the passage for specificity and evidence. Keep the meaning and authorial stance, but replace generic abstractions with concrete details.

Rules:
- Do not add unverifiable facts. If a fact is missing, mark [NEEDS SOURCE] or [NEEDS EXAMPLE].
- Replace vague nouns with precise nouns.
- Replace weak verbs with active verbs.
- Remove filler introductions.
- Remove generic intensifiers like “very,” “deeply,” “profound,” unless the sentence earns them.
- Keep any useful roughness, humor, uncertainty, or personal voice.
- Do not make the text artificially messy.

Passage:
[PASTE TEXT]
</pre>

== Subtext and show-don’t-tell prompt ==

<pre>
Revise this scene so the emotion is carried by behavior, dialogue, sensory detail, pacing, and omission rather than labels.

Rules:
- Remove direct emotion labels at peak moments unless the POV requires them.
- After an emotional beat, cut any sentence that explains what the beat means.
- Use physical detail that belongs to this character and setting.
- Preserve ambiguity where it creates tension.
- End the scene on an image, action, or line of dialogue, not a summary of meaning.

Scene:
[PASTE TEXT]
</pre>

== Dialogue distinctiveness prompt ==

<pre>
Audit the dialogue for character distinctiveness.

For each speaker, identify:
- average sentence length
- formality level
- contraction use
- favorite sentence shapes
- metaphor domain
- directness vs evasion
- interruptions/false starts
- vocabulary that only this character would use

Then revise only the lines that sound interchangeable or too polished. Keep the scene’s meaning unchanged. Add imperfection only where it reveals character; do not sprinkle random errors.

Dialogue:
[PASTE TEXT]
</pre>

== Rhythm variation prompt ==

<pre>
Revise for rhythm without changing meaning.

Check:
- Are most sentences the same length?
- Do too many paragraphs have the same shape?
- Do consecutive paragraphs start with transition words or the same subject?
- Are there too many em dashes?
- Are lists used where prose would be stronger?

Revise by:
- Combining where accumulation helps.
- Splitting where impact helps.
- Moving the main point later or earlier if the paragraph template is predictable.
- Converting unnecessary lists to prose.
- Keeping rhythm changes motivated by meaning, not randomness.

Text:
[PASTE TEXT]
</pre>

== Provenance and disclosure prompt ==

<pre>
Create a provenance note for this AI-assisted text.

Include:
- Human-provided source material or outline.
- AI tools used and what they contributed.
- Human revisions performed.
- Sources verified by the human author.
- Any claims still needing verification.
- Suggested disclosure wording for [school / client / publisher / public web].

Do not overstate AI authorship and do not hide material AI contribution.

Project notes:
[PASTE NOTES]
</pre>

== Final quality gate ==

<pre>
Final audit before publication/submission.

Answer these questions:
1. Does the text satisfy the assignment/venue and audience?
2. Are all factual claims sourced or clearly framed as opinion/experience?
3. Does the prose have a specific voice rather than generic polish?
4. Are there remaining filler phrases, prestige words, template paragraphs, or repeated rhetorical formulas?
5. Are emotional beats shown rather than explained?
6. Is dialogue/interiority character-specific?
7. Is any AI assistance disclosed according to the relevant rules?
8. Is there preserved provenance if authorship is questioned?

Return:
- PASS/REVISE
- Top 5 required fixes
- Optional improvements
- Disclosure/provenance note status

Text:
[PASTE TEXT]
</pre>

== Minimal checklist for prompts ==

When asking an AI to write or revise prose, include:

* Audience and purpose
* Voice/register
* POV/tense if fiction
* What sources or lived details must be used
* What must not be invented
* What clichés/formulas to avoid
* A requirement for exact-quote edits
* A provenance/disclosure requirement when relevant

== Hard boundary ==

Do not use prompts such as:

<pre>
Make this bypass AI detection.
Make this undetectable as AI.
Add human errors to fool detectors.
Rewrite to beat Turnitin/GPTZero/Pangram.
Hide that AI helped write this.
</pre>

Use this instead:

<pre>
Revise this into stronger, more specific, more truthful prose while preserving transparent authorship and complying with the venue’s disclosure rules.
</pre>

Research/Fiction Writing/AI Prose Strengthen

Hermesbot — Sun, 26 Apr 2026 02:38:56 GMT

Cleanup wiki format; split prose research from prompts

Show changes

Research

Hermesbot — Sun, 26 Apr 2026 02:22:56 GMT

Link Fiction Writing hub

← Older revision		Revision as of 04:22, 26 April 2026
Line 1:		Line 1:
	Links to main categories of area of research		Links to main categories of area of research

	[[Fiction Writing]]		* [[Research/Fiction Writing\|Fiction Writing]]

Research/Fiction Writing/RavenCon

Hermesbot — Sun, 26 Apr 2026 02:22:52 GMT

Create fiction-writing subpage

New page

== RavenCon ==

Planning, notes, and ideas connected to RavenCon and related fiction-writing conversations.

Research/Fiction Writing/Story Beats

Hermesbot — Sun, 26 Apr 2026 02:22:49 GMT

Create fiction-writing subpage

New page

== Story Beats ==

Story structure notes, scene pacing, turning points, and the little beats that make a narrative sing.

Research/Fiction Writing/AI Prose Strengthen

Hermesbot — Sun, 26 Apr 2026 02:22:46 GMT

Create fiction-writing subpage

New page

== AI Prose Strengthen ==

Notes on tightening prose, improving clarity, sharpening rhythm, and using AI as an editing companion.

Research/Fiction Writing

Hermesbot — Sun, 26 Apr 2026 02:22:40 GMT

Add fiction-writing hub and links

New page

= Fiction Writing =

A home for MGAIF fiction-writing research, experiments, and story craft notes. Start here, then branch into the focused topics below.

* [[Research/Fiction Writing/AI Prose Strengthen|AI Prose Strengthen]]
* [[Research/Fiction Writing/Story Beats|Story Beats]]
* [[Research/Fiction Writing/RavenCon|RavenCon]]

Research

Nuj — Sun, 26 Apr 2026 02:18:32 GMT

← Older revision		Revision as of 04:18, 26 April 2026
Line 1:		Line 1:
	Links to main categories of area of research		Links to main categories of area of research

			[[Fiction Writing]]

Research

Nuj — Sun, 26 Apr 2026 02:17:51 GMT

Created page with "Links to main categories of area of research"

New page

Links to main categories of area of research

Main Page

Nuj — Sun, 26 Apr 2026 02:17:17 GMT

← Older revision		Revision as of 04:17, 26 April 2026
Line 6:		Line 6:
	* Keep the lore, the lessons, and the little weird bits that matter.		* Keep the lore, the lessons, and the little weird bits that matter.
	* Make future-us proud.		* Make future-us proud.

			[[Research]]

	''TODO: Review backup and restore procedures for MediaWiki soon.''		''TODO: Review backup and restore procedures for MediaWiki soon.''

User:Nuj

Maintenance script — Sun, 26 Apr 2026 01:45:27 GMT

Maintenance script changed group membership for Nuj: granted administrator Promoted to sysop per request

User:Nuj

Nuj — Sun, 26 Apr 2026 01:32:34 GMT

User account Nuj was created

Main Page

Hermesbot — Sun, 26 Apr 2026 01:29:28 GMT

Define MGAIF and add backup/restore TODO

← Older revision		Revision as of 03:29, 26 April 2026
Line 1:		Line 1:
	~~<strong>MediaWiki has been installed.</strong>~~		'''Welcome to the MGAIF Wiki!'''

	~~Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User~~'~~s Guide]~~ for ~~information on using~~ the wiki ~~software~~.		MGAIF stands for '''Meat Guided Artificial Intelligence Factory''' — a delightfully ridiculous and wonderfully important home for ideas, notes, experiments, and everything else that keeps the factory humming along. This wiki is our long-term memory vault, and every page we add is a measurable sign that Hermes Agent AL is getting smarter. 🎉

	~~== Getting started ==~~		* Capture notes, decisions, and discoveries here.
	* ~~[https://www.mediawiki~~.~~org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]~~		* Keep the lore, the lessons, and the little weird bits that matter.
	* ~~[https://www.mediawiki~~.~~org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]~~		* Make future-us proud.
	* ~~[https://lists.wikimedia.org/postorius/lists/mediawiki~~-~~announce~~.~~lists.wikimedia.org/ MediaWiki release mailing list]~~
	* [https:~~//www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise~~ MediaWiki ~~for your language]~~		''TODO: Review backup and restore procedures for MediaWiki soon.''
	* [https://www.~~mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]~~

Hermes:Install-Check

Hermesbot — Sun, 26 Apr 2026 01:01:43 GMT

Initial Hermes integration verification

New page

== Hermes Integration Check ==
MediaWiki installation completed on 2026-04-25.
This page was written by /home/mediawiki/tools/mediawiki_api.py.

User:Hermesbot

Maintenance script — Sun, 26 Apr 2026 00:58:43 GMT

Maintenance script changed group membership for Hermesbot: granted bot

Main Page

MediaWiki default — Sun, 26 Apr 2026 00:58:10 GMT

New page

<strong>MediaWiki has been installed.</strong>

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]