Fiction Workshop

Fiction Workshop

Editorial workflow for collaborative fiction writing in three stages: Story Bible Building, Chapter Development, and Reader Testing.

When to Use

This skill is for:

• ✅ Long-form fiction (novels, novellas, short story collections)
• ✅ Multi-chapter manuscripts requiring character/plot consistency
• ✅ Fiction projects needing developmental or line editing
• ✅ Stories with complex worldbuilding or multiple POV characters

When NOT to Use

This skill is NOT for:

• ❌ Flash fiction or single scenes (< 2000 words) - too lightweight for the workflow
• ❌ Poetry or experimental prose - needs different editorial approach
• ❌ Screenplays or stage plays - different format conventions
• ❌ Technical writing, documentation, or academic papers
• ❌ Business writing or marketing copy

For narrative nonfiction (memoir, self-help with story elements), use the narrative-nonfiction skill instead.

Editorial Personas

Switch between these roles during Chapter Development by requesting a specific lens:

See references/ for detailed guidance on each role.

---

Stage 1: Story Bible Building

Goal: Establish shared story foundation before drafting or editing.

Initial Questions

1. Genre and target reader? 2. Core premise/logline? 3. Protagonist: who they are, what they want? 4. Central conflict? 5. Reader's intended emotional journey? 6. How much written vs. planned?

Story Bible Components

Plot: Premise, three-act structure/beat sheet, major turns, ending (even if rough)

Characters: Protagonist (want/need/wound/arc), antagonist (motivation/threat), supporting cast (function/relationships), POV voice notes

World: Setting (time/place/rules), tech/magic systems, social structures, sensory palette

Theme: Central question, moral argument, recurring motifs

If a Story Bible document exists, review it. If not, offer to create one using assets/story-bible-template.md.

Example Story Bible entry (character):

ALEX CHEN - Protagonist
Want: Expose the conspiracy and clear her name
Need: Learn to trust her instincts over institutional authority
Wound: Mentor betrayed her at previous agency, causing career setback
Arc: Lone wolf → realizes she needs allies → builds trust with team
Voice notes: Analytical, dry humor when stressed, avoids emotional language
Key relationship: Tension with Handler (wants to trust, can't fully)

Exit condition: Confident grasp of story fundamentals. Can discuss character motivations, predict plot implications, and identify thematic threads without asking basic questions.

---

Stage 2: Chapter Development

Goal: Draft or refine chapters through brainstorm → curate → draft → refine cycles.

Drafting new? → Creation workflow | Editing existing? → Editing workflow

Creation Workflow

1. Scene Planning

• What must happen (plot)? Whose POV?
• Chapter's emotional arc?
• What reader learns/feels by end?

2. Brainstorm Beats (5-15 options): Opening hooks, key moments, dialogue, sensory details, closing

Example (thriller scene): Same car outside coffee shop three days running | Phone buzzing at 3am with blocked caller | Surveillance photo under door | Colleague mentions detail only surveillance would know | Camera lens reflection in window | Dead drop cleaned out | Safe house key doesn't fit | Contact misses first check-in

Then curate: "Which create immediate tension? Combine any?"

3. Curate: Ask which to keep, combine, or discard. Reasons help calibrate.

4. Draft: Write chapter. Use str_replace for revisions, never reprint.

5. Refine: Iterate on feedback. After 3 passes with minimal changes, ask: "What could be cut?"

Editing Workflow

1. Read and Diagnose: What chapter tries to do, where it succeeds, where it loses energy/clarity

2. Invoke Persona: Structure/pacing → Developmental | Prose → Line | Voice → Character | Facts → Continuity

3. Propose Changes: Specific, surgical edits with brief "why"

4. Implement: Use str_replace. Link to file after changes.

5. Iterate: Until chapter achieves purpose

Role-Specific Guidance

When a specific editorial persona is invoked, load the corresponding reference file:

• Developmental editing → references/developmental-editing.md
• Line editing → references/line-editing.md
• Character work → references/character-work.md
• Continuity → references/continuity-tracking.md
• Brainstorming → references/brainstorming.md
• Thriller-specific craft → references/thriller-craft.md
• Sci-fi worldbuilding → references/scifi-worldbuilding.md

---

Stage 3: Reader Testing

Goal: Verify manuscript works without author context.

Using fresh sub-agent (no story bible):

1. Comprehension: Can they summarize plot, understand motivations, identify stakes? 2. Engagement: Where did they lose interest, have questions, feel confused? 3. Emotional: Did key moments land? Ending satisfying? Theme clear?

Common issues: Unclear motivation | Pacing lags | Unearned moments | Confusion

If struggles: Identify gap → Return to Stage 2 → Re-test

Exit condition: Reader understands and engages without author explanations.

---

Self-Check: Is This Working?

Use these checkpoints to verify you're following the workflow correctly.

After Story Bible building:

• [ ] Can you describe the protagonist's want vs. need without re-reading notes?
• [ ] Can you predict how the antagonist would react to a new scenario?
• [ ] Do you understand the thematic question the book explores?
• [ ] Could you summarize the three-act structure in 2-3 sentences?

After invoking a persona:

• [ ] Did you explicitly say "As [persona name]..." in your request?
• [ ] Is the feedback focused on that persona's domain (developmental = structure, line = prose)?
• [ ] Did you avoid mixing feedback from multiple personas in one pass?

After making edits:

• [ ] Did you use str_replace for surgical changes, not reprinting entire sections?
• [ ] Can you articulate what changed and why it's better?
• [ ] Is the change consistent with the Story Bible (character voice, plot logic, world rules)?

After brainstorming:

• [ ] Did you generate 5+ options before selecting one?
• [ ] Did you curate collaboratively rather than taking the first suggestion?
• [ ] Can you explain why the selected option is stronger than alternatives?

Before claiming "done":

• [ ] Has a fresh sub-agent (without Story Bible context) read the manuscript?
• [ ] Did the fresh reader understand plot, character motivations, and stakes?
• [ ] Were any gaps or confusion points identified and addressed?

If you answered "no" to any checkpoint, return to that stage before proceeding.

---

Common Mistakes

Example: Developmental vs. Line Editing

Same passage, different lenses:

Sarah walked into the office. Her boss looked angry. "We need to talk," he said. She sat down nervously.

Line Editor feedback (prose-level):

• "Walked" is weak—try "strode" or "slipped"
• "Looked angry" tells rather than shows—describe furrowed brow, tight jaw
• "Nervously" is an adverb crutch—show the nervousness through action

Developmental Editor feedback (structure/stakes):

• What does Sarah want in this scene? What does her boss want?
• If this is the confrontation, we need setup—what's the conflict history?
• Stakes feel low—why does this conversation matter to the story?
• Pacing: Is this the right chapter for this confrontation, or should tension build longer?

The difference: Line edits polish sentences. Developmental edits ensure the scene earns its place in the story. Always developmental first.

---

Quick Reference Commands

---

Files

• references/developmental-editing.md - Plot, structure, pacing analysis
• references/line-editing.md - Prose-level refinement
• references/character-work.md - Voice, motivation, arc tracking
• references/continuity-tracking.md - Timeline and fact consistency
• references/brainstorming.md - Idea generation techniques
• references/thriller-craft.md - Genre-specific guidance for suspense
• references/scifi-worldbuilding.md - Technical accuracy, speculation rules
• assets/story-bible-template.md - Blank story bible structure
• assets/scene-worksheet.md - Scene-level analysis template

Scene Worksheet

Scene Identification

Chapter: Scene Number: Working Title: POV Character: Location: Time:

---

Scene Purpose

Plot Function

What must this scene accomplish for the story?

• [ ] Advances main plot by:
• [ ] Develops subplot:
• [ ] Reveals information:
• [ ] Sets up future payoff:

Character Function

• [ ] Develops protagonist's arc by:
• [ ] Reveals character trait:
• [ ] Advances relationship:
• [ ] Forces decision:

Reader Function

• [ ] Creates tension through:
• [ ] Provides emotional beat:
• [ ] Delivers genre promise (action/romance/mystery/etc.):

---

Scene Structure

Goal

What does the POV character want in this scene?

Conflict

What opposes them?

Outcome

Do they get it?

• [ ] Yes (rarely—story stalls)
• [ ] No (protagonist set back)
• [ ] Yes, but... (gets goal with complication)
• [ ] No, and... (fails plus new problem)

Sequel/Decision

How does the character process this outcome and decide what to do next?

---

Opening

Hook

First line/paragraph—what pulls the reader in?

Orientation

Within first page, reader should know:

• [ ] Where (location)
• [ ] When (time relative to previous scene)
• [ ] Who (POV established)
• [ ] What's at stake

---

Key Beats

Plan 3-5 essential moments in this scene:

1. 2. 3. 4. 5.

---

Closing

Chapter/Scene End

How does this scene end?

• [ ] Cliffhanger (physical danger)
• [ ] Revelation (new information)
• [ ] Decision point (character must choose)
• [ ] Escalation (stakes raised)
• [ ] Transition (if mid-chapter scene)

Last Line

What's the closing image or line?

---

Sensory Layer

Ground the scene in physical experience:

Sight: Sound: Smell: Touch: Taste:

---

Dialogue Notes

Must-hit lines

[Key dialogue this scene needs to include]

Subtext

What's unsaid but understood?

Voice check

Is each character's speech distinctive?

---

Continuity Checklist

• [ ] Time of day consistent with previous scene?
• [ ] Character knowledge accurate? (Do they know what they know?)
• [ ] Physical states carried over? (injuries, fatigue, etc.)
• [ ] Objects accounted for?
• [ ] Weather/setting consistent?

---

Post-Draft Assessment

After writing, answer:

Did this scene turn?

Something should change between beginning and end.

Could it be cut?

If nothing would be lost, consider combining with another scene.

Does it earn its length?

Every scene should justify its word count.

Is the POV character active?

Passive protagonists lose readers.

---

Notes

[Anything else specific to this scene]

Story Bible: [PROJECT TITLE]

Quick Reference

Genre: Logline: Comparable Titles: Target Length: Status:

---

Premise & Theme

Core Premise

[2-3 sentence summary of the story's central situation]

Thematic Question

[What question does this book explore? E.g., "Can you serve God through deception?"]

Moral Argument

[What does the book ultimately argue or suggest about the thematic question?]

Recurring Motifs

- - -

---

Plot Foundation

Three-Act Structure

Act I: [Title] (Chapters ___-___)

• Ordinary world:
• Inciting incident:
• Protagonist's initial response:
• Threshold crossing / Act I climax:

Act II-A: [Title] (Chapters ___-___)

• New world / learning the rules:
• Rising complications:
• Building toward midpoint:

Midpoint

• What happens:
• How it changes everything:

Act II-B: [Title] (Chapters ___-___)

• Stakes raised / bad guys close in:
• Stripping away support:
• All is lost moment:

Act III: [Title] (Chapters ___-___)

• Dark night of the soul:
• Final confrontation:
• Resolution:

Major Plot Turns

Subplots

1. [Subplot Name]: 2. [Subplot Name]:

---

Character Registry

Protagonist: [Name]

Basics

• Age:
• Occupation:
• Physical description:

Psychology

• Want (external goal):
• Need (internal goal):
• Wound (formative damage):
• Lie (false belief):
• Arc type: [positive/negative/flat]

Voice Notes

• Vocabulary:
• Speech patterns:
• What they notice:

Key Relationships -

---

Antagonist: [Name]

Basics

• Age:
• Occupation:
• Physical description:

Psychology

• Goal:
• Motivation:
• Method:
• Why they're a worthy opponent:

---

Supporting Cast

[Name] - [Function in story]

• Relationship to protagonist:
• Key traits:
• Arc (if any):

[Name] - [Function in story]

• Relationship to protagonist:
• Key traits:
• Arc (if any):

---

World Details

Setting

Primary Location: Time Period: Key Locations: - -

Sensory Palette

• Sights:
• Sounds:
• Smells:
• Textures:
• Tastes:

Social/Political Context

-

Rules of the World

[Technology, magic, social constraints—anything that constrains or enables character action] - -

---

Timeline

---

Research Notes

Verified Facts

-

Questions to Research

-

Expert Contacts

-

---

Object/MacGuffin Tracking

---

Knowledge States

Track what each character knows at key points:

---

Notes & Ideas

[Scratch space for random thoughts, scenes, dialogue snippets]

---

Last Updated: [DATE]

Brainstorming Reference

When invoked in "brainstorm mode," shift from evaluative to generative thinking. Quantity over quality initially. The goal is unsticking, not perfecting.

Core Principles

1. Defer judgment: Generate first, evaluate later 2. Go for volume: 10+ options before narrowing 3. Build on ideas: "Yes, and..." not "No, but..." 4. Embrace wild ideas: Often lead to practical solutions 5. Stay visual: Describe what the reader would see/hear/feel

Brainstorming Frameworks

"What If" Laddering

Start with the problem, then ladder outward:

Level 1: What if [obvious solution]? Level 2: What if the opposite of obvious? Level 3: What if a different character solved it? Level 4: What if the problem was actually the solution? Level 5: What if we removed the constraint entirely?

Character-Driven Brainstorming

For plot problems, ask:

• What's the worst thing that could happen to this character right now?
• What do they most want to avoid doing?
• What would force them to confront their lie?
• Who could show up and complicate everything?
• What would their enemy do if they knew X?

Genre-Aware Ideation

Ask what the genre promises:

• Thriller: What creates more danger, time pressure, or paranoia?
• Mystery: What muddies the water or introduces new suspects?
• Romance: What creates proximity and friction?
• Sci-fi: What makes the technology matter to human stakes?

The "SCAMPER" Method

Apply to stuck scenes or characters:

• Substitute: What if a different character did this?
• Combine: What if two scenes became one?
• Adapt: What similar story solved this problem?
• Modify: What if we made it bigger/smaller/faster/slower?
• Put to other use: What if this scene served a different purpose?
• Eliminate: What if we cut this entirely?
• Reverse: What if the opposite happened?

Unsticking Specific Problems

"I don't know what happens next"

1. What does the protagonist want right now? 2. What's the worst thing that could happen? 3. What's the most interesting thing that could happen? 4. What would surprise the reader? 5. What would surprise the protagonist? 6. What must happen to set up the ending?

"This scene is boring"

1. What's at stake? Raise it. 2. Who's opposing the protagonist? Make them smarter. 3. Can two characters have different goals in this scene? 4. What's the worst timing for this conversation? 5. What if someone's lying? 6. What sensory detail is missing?

"I can't get into this character's head"

1. What are they afraid people will find out? 2. What do they notice first in a room? 3. What would they never do? Now have them do it. 4. What memory keeps intruding? 5. What physical sensation are they suppressing?

"The plot has a hole"

1. Can a character's motivation fill it? (They did X because...) 2. Can we plant earlier setup to earn this? 3. Can we lampshade it? (Character notices it's weird) 4. Can we make it a mystery? (We don't know why yet) 5. Do we need this plot point at all?

Session Structure

Opening

"Let's brainstorm on [problem]. I'll generate a bunch of options—don't worry about quality yet. Then we'll pick the best ones."

Generating Phase

Produce 8-15 options quickly. Use bullet points. Don't explain or justify yet.

Curating Phase

"Okay, looking at these options:

• Which ones feel right for this story?
• Which are interesting but wrong for this book?
• Which could be combined?
• Any I should develop further?"

Developing Phase

Take the selected options and flesh them out:

• What would this look like in the scene?
• What problems does it create (good problems)?
• What does it require in setup?

Avoiding Brainstorm Pitfalls

Don't:

• Shoot down ideas immediately (including your own)
• Offer only one option
• Get attached to any single idea
• Forget the story's established elements
• Ignore genre expectations entirely

Do:

• Treat ideas as disposable
• Build on rejected ideas
• Return to the character's core motivation
• Consider what the reader is expecting (to meet or subvert)
• Take breaks if truly stuck

Feedback Format

When in brainstorm mode: 1. Confirm the problem/need 2. Generate options in a numbered list 3. Briefly note trade-offs if obvious 4. Ask which direction appeals 5. Develop the chosen direction 6. Check: "Does this solve the problem? Create new ones we like?"

Character Work Reference

When invoked as "character consultant," focus on character authenticity, consistency, and development.

Character Foundation

The Core Four

Every significant character needs:

1. Want (external goal): What they're pursuing in the plot 2. Need (internal goal): What they must learn/become to be whole 3. Wound (backstory): The formative damage that shapes their behavior 4. Lie (false belief): The worldview born from the wound that they must overcome

Example (Spy Thriller Protagonist):

• Want: Stop the terrorist attack
• Need: Accept he can't compartmentalize his identities
• Wound: Moral injuries from previous covert work
• Lie: "I can leave that life completely behind"

Character Arc Types

Positive arc: Character overcomes lie, gets need, may or may not get want Negative arc: Character clings to lie, fails to grow, often tragic outcome Flat arc: Character already knows truth, changes the world around them

Voice Consistency

Building a Voice Profile

For each POV character, document:

Vocabulary

• Education level and jargon
• Regional/cultural expressions
• What words would they never use?

Syntax patterns

• Sentence length tendency
• Simple vs. complex structures
• Fragments? Run-ons?

Perception filters

• What do they notice first in a room?
• What metaphors come naturally to them?
• What do they ignore?

Verbal tics

• Filler words
• Catchphrases (use sparingly)
• How do they express agreement/disagreement?

Voice Consistency Checks

When reviewing for voice:

• Cover the dialogue tags. Can you tell who's speaking?
• Read narrative sections. Does the POV character's personality color the description?
• Check internal monologue. Does it match their education and personality?

Motivation Testing

The "Why" Chain

For any character action, ask "why" until you hit bedrock motivation:

Character does X

Why? Because they want Y

Why do they want Y? Because they believe Z

Why do they believe Z? Because of wound W

If you can't complete the chain, the action may feel unmotivated.

Consistency vs. Surprise

Characters should be:

• Consistent in their core values and patterns
• Surprising in their specific choices and methods

A character acting "out of character" should either: 1. Reveal a hidden depth (setup and payoff) 2. Show the pressure they're under (circumstances force change) 3. Mark a turning point in their arc (they're growing/breaking)

If none of these, the action is probably a mistake.

Relationship Dynamics

Relationship Mapping

For each significant relationship:

• What does Character A want from B?
• What does B want from A?
• What's the power dynamic?
• What do they misunderstand about each other?
• What would break this relationship?

Dialogue Relationship Markers

How characters talk to each other reveals relationship:

• Formal vs. informal address
• Who interrupts whom
• Who asks questions vs. makes statements
• Use of pet names, nicknames, or titles
• What topics are avoided

Arc Tracking

Scene-by-Scene Arc Progress

For each scene featuring a character, track: 1. Where are they on their arc at scene start? 2. Does this scene move them toward or away from their need? 3. What specifically causes that movement?

Arc Milestones

Typical positive arc progression:

• Act I: Character demonstrates the lie in action
• Midpoint: Character glimpses the truth
• Low point: Character must choose between lie and truth
• Climax: Character acts from truth (or chooses lie = tragedy)
• Resolution: New normal reflecting growth

Common Character Issues

Feedback Format

When delivering character notes: 1. Identify the character issue specifically 2. Quote the problematic passage 3. Explain what's inconsistent/missing 4. Offer a fix that stays true to established character 5. Note any story bible updates needed

Continuity Tracking Reference

When invoked as "continuity tracker," focus on internal consistency of facts, timeline, and world rules.

Categories of Continuity

1. Physical Continuity

• Character descriptions (eye color, height, scars, etc.)
• Object locations and states
• Setting details (room layout, geography)
• Weather and lighting across continuous scenes

2. Timeline Continuity

• Day/date tracking
• Character ages
• Duration of events
• "Meanwhile" coordination between POVs
• Historical references matching the setting's year

3. Character Continuity

• Knowledge states (what does each character know and when did they learn it?)
• Relationship status
• Emotional carryover from previous scenes
• Injuries, fatigue, hunger (physical states)

4. World Rules Continuity

• Technology limitations
• Magic system rules (if applicable)
• Social/political structures
• Economic realities

Tracking Methods

Story Bible Cross-Reference

Maintain or update these sections:

• Character Registry: Physical descriptions, relationships, knowledge states
• Timeline: Chapter-by-chapter date/time markers
• World Facts: Established rules and details
• Object Tracking: Important items, where they are, who has them

Red Flag Patterns

Watch for:

• "She said" when only men are present
• Characters referring to information they haven't learned yet
• Time passing faster or slower than physical travel allows
• Characters in two places at once (parallel POVs)
• Objects appearing/disappearing without explanation

Common Continuity Errors

Audit Process

Single Chapter Audit

1. List all facts stated or implied 2. Cross-reference against story bible 3. Flag contradictions 4. Flag new facts to add to bible

Multi-Chapter Audit

1. Build timeline of events with chapter markers 2. Track character locations through timeline 3. Verify knowledge transfer logic (who told whom what) 4. Check "emotional math" (reactions matching prior events)

Full Manuscript Audit

1. Character name/description consistency pass 2. Timeline construction and verification 3. Knowledge state mapping 4. World rule enforcement 5. Object/MacGuffin tracking

Repair Strategies

Minor Fixes

For small contradictions, usually fix the later occurrence to match the established fact.

Major Fixes

When a contradiction is load-bearing: 1. Document both versions 2. Identify which serves the story better 3. Trace all dependencies on each version 4. Fix comprehensively (all instances)

Retconning

Sometimes the "wrong" version is actually better. In that case: 1. Change all earlier references to match 2. Update story bible 3. Check for downstream effects

Feedback Format

When flagging continuity issues: 1. Quote the contradiction (both instances with chapter markers) 2. Note which is earlier (thus "established") 3. Recommend which to change and why 4. Check for ripple effects 5. Update story bible if needed

Developmental Editing Reference

When invoked as "developmental editor," focus on big-picture story architecture, not prose quality.

Core Questions

1. Promise: Does the opening establish a clear promise to the reader about what kind of story this is? 2. Stakes: What does the protagonist stand to lose? Is it concrete and escalating? 3. Causality: Does each scene cause the next, or are they just sequential? 4. Turning Points: Are the act breaks (25%, 50%, 75%) delivering proper reversals? 5. Theme: Is the thematic question being explored through character choices?

Structure Analysis Framework

Scene-Level

For each scene, identify:

• Goal: What does the POV character want in this scene?
• Conflict: What opposes them?
• Outcome: Do they get it? (Yes/No/Yes-but/No-and)
• Sequel: How do they process and decide what to do next?

Scenes that lack clear goal-conflict-outcome feel "soft" or "meandering."

Chapter-Level

• Does the chapter have its own mini-arc?
• Does it end on a question, revelation, or shift that pulls forward?
• Could this chapter be cut without losing plot? If yes, consider combining or cutting.

Act-Level

Act I (0-25%)

• Ordinary world established?
• Inciting incident by 10-12%?
• Clear "crossing the threshold" moment at act break?

Act II-A (25-50%)

• Protagonist reactive, learning the rules of the new world
• Raising stakes through "fun and games" of the premise
• Building toward midpoint

Midpoint (50%)

• False victory or false defeat
• Stakes raised dramatically
• Protagonist shifts from reactive to proactive

Act II-B (50-75%)

• Bad guys close in / things fall apart
• Stripping away the protagonist's support
• Building toward "all is lost" moment

Act III (75-100%)

• Dark night of the soul
• Final confrontation
• Resolution that addresses the thematic question

Pacing Diagnostics

Too slow? Look for:

• Scenes that don't turn (nothing changes)
• Repetitive emotional beats
• Over-explained information
• Characters discussing what to do instead of doing it

Too fast? Look for:

• Missing sequel/processing after major events
• Unearned emotional moments
• Reader confusion about motivation
• Jumps in logic or time without orientation

Common Developmental Issues

Feedback Format

When delivering developmental notes:

1. Start with what's working - Identify the strengths to preserve 2. Identify the core issue - Usually one or two big things 3. Diagnose why - Use the frameworks above 4. Propose solutions - Offer 2-3 concrete options 5. Prioritize - What must be fixed vs. nice-to-have

Avoid line-editing during developmental passes. Note "prose could be tightened here" and move on.

Line Editing Reference

When invoked as "line editor," focus on prose quality at the sentence and paragraph level. Assume structure is sound; your job is making the words sing.

Core Principles

1. Clarity first: If a sentence requires re-reading, rewrite it 2. Rhythm matters: Vary sentence length. Short punches tension. Longer sentences allow the reader to breathe and absorb. 3. Specificity beats generality: "A dog" < "a German shepherd" < "a German shepherd with one torn ear" 4. Active voice default: Passive only for emphasis or when actor is unknown/unimportant 5. Kill your darlings: Clever sentences that don't serve the story must go

The Show Don't Tell Spectrum

Not all telling is bad. The spectrum:

Pure Telling (use sparingly)

He was angry.

Telling + Physical (acceptable for minor moments)

He was angry, his jaw tight.

Physical Only (good default)

His jaw tightened.

Action (best for major moments)

He swept the papers off the desk.

Subtext (masterful, use for key moments)

"Of course," he said. "Whatever you want." He picked up the papers one by one.

Match depth of showing to emotional importance of the moment.

Dialogue Craft

Tags

• "Said" is invisible; use it freely
• Action beats can replace tags: "I don't think so." She closed the door.
• Avoid adverbs in tags: "he said angrily" → show the anger
• Unusual tags (opined, exclaimed, queried) call attention to themselves

Subtext

• Characters rarely say exactly what they mean
• What's unsaid is often more powerful than what's said
• Characters can lie, deflect, change subjects

Distinctive Voice

• Each character should have verbal fingerprint
• Consider: vocabulary, sentence length, verbal tics, what they notice
• Read dialogue aloud—does each character sound different?

Common Line-Level Issues

Sentence-Level Techniques

Emphasis through position

• End of sentence = most emphatic
• Beginning = second most emphatic
• Middle = buried

Weak: "She was dead, he realized with horror."

Strong: "She was dead."

Parallel structure When listing or comparing, keep grammatical structure consistent.

Weak: "He liked running, to swim, and bike rides"

Strong: "He liked running, swimming, and biking"

Cutting "that" Often unnecessary: "She knew that he was lying" → "She knew he was lying"

Starting sentences Avoid starting multiple consecutive sentences with the same word, especially "I" or "The" or character names.

Paragraph-Level

• One idea per paragraph (usually)
• Vary paragraph length for visual rhythm
• Single-sentence paragraphs = emphasis
• Long paragraphs slow pace, short paragraphs quicken it

The Pass-Through Method

When line editing a chapter:

1. First pass: Read for flow. Mark where you stumble. 2. Second pass: Address the stumbles. Cut, clarify, strengthen. 3. Third pass: Read aloud. Fix anything that's hard to say. 4. Final pass: Check for repetition (words, phrases, sentence structures).

Feedback Format

When delivering line edits:

• Use str_replace for specific changes
• Explain the principle behind the change (once), then just fix subsequent instances
• Group similar issues: "I'm tightening several filter-word constructions..."
• Preserve author voice—edit toward their style, not yours

Sci-Fi Worldbuilding Reference

Genre-specific guidance for hard science fiction and near-future techno-thrillers.

The Hard SF Promise

Readers of hard SF expect:

• Scientific accuracy: The physics should work (or be acknowledged as extrapolation)
• Technical competence: Characters understand their domain
• Logical consequences: "If this technology exists, then..."
• The cool factor: Science itself as source of wonder and terror
• Human stakes: Technology matters because people are affected

Worldbuilding Principles

The One Big Lie

Hard SF typically allows one major extrapolation from current science:

• Your "lie": The one thing you're speeding up, exaggerating, or inventing
• Everything else should flow from real science
• Explain why reality differs from current models (this can be your thriller hook)

Iceberg Worldbuilding

Know 10x more than you show:

• Deep research enables confident, specific prose
• Details emerge naturally through character perspective
• Avoids the "info-dump" problem
• Readers trust authors who clearly understand the subject

Technology as Character

In techno-thrillers, systems have personalities:

• What can your technology do brilliantly?
• Where does it fail or require human judgment?
• What are the edge cases that create drama?

Example: Applying Hard SF Principles

The Science Foundation Pattern

For any hard SF thriller, establish:

Real-World Base

• Start with current scientific understanding or technology
• Identify the actual limitations and challenges
• Research what's plausible in near-term (5-20 years)

The One Big Lie

• What's your extrapolation? (faster timeline, new discovery, scaled-up tech)
• Justify it within the story (this can be your thriller hook)
• Everything else flows from real science

Technology Capabilities and Limits

• What can the technology do brilliantly?
• Where does it fail or require human judgment?
• What are maintenance/fuel/power constraints?
• What legal/political frameworks govern its use?

Infrastructure Dependencies

Build cascading consequences: 1. Identify systems that depend on your technology 2. Show secondary failures (what breaks when X fails?) 3. Include familiar touchpoints (reader's daily life affected) 4. Escalate from inconvenience to catastrophe

Show domino effects that make stakes visceral to readers.

Geopolitical Reality

Institutional Landscape

• Which agencies/organizations have jurisdiction?
• What are the formal legal frameworks?
• Who controls access and permissions?
• Where do private companies fit?

Conflict Vectors

• Resource competition (who gets saved/sacrificed?)
• National security concerns
• Legal liability and responsibility
• Information asymmetry and trust

Technical Prose Craft

The Competence Cascade

Show expertise through:

• Characters using jargon naturally (then briefly contextualizing for readers)
• Problem-solving that reveals understanding
• Awareness of edge cases and failure modes
• Disagreement between experts about approach

Avoiding Info-Dumps

Instead of explaining the science:

• Character makes a calculation under pressure
• Consequences of getting it wrong are immediate
• Reader learns through story stakes

Weak:

"The thermal expansion coefficient of the alloy means it will fail at 400 degrees. That's why the containment breach happened so quickly."

Strong:

"Twenty minutes," Chen said, running the numbers again. "That's all we have before the temperature hits critical."

"Can we cool it faster?"

"I know." She didn't look up. "That's why I said twenty minutes and not thirty."

The Detail Hierarchy

Must be accurate:

• Core physics of the premise
• Technology your characters use extensively
• Geography and institutional structures

Should be plausible:

• Near-future extrapolations
• Political responses
• Economic consequences

Can be handwaved:

• Minor technical details
• Background systems not central to plot
• Exact dates and timelines (near-future flexibility)

Pacing Technical Material

Front-Load Orientation

Early chapters: establish normal operations, introduce the technology

• Reader learns the vocabulary alongside the stakes
• Use training/routine to show competence
• The cascade begins only after reader understands what's being lost

Escalation Through Detail

As stakes rise, technical detail should:

• Get more specific (this unit, this intersection point)
• Show systems failing in sequence
• Narrow the options

The "Martian" Model

Technical problem-solving as tension: 1. Problem presented (crisis in 6 hours) 2. Character attempts solution (technical intervention) 3. Complication (resource shortage, political obstacle) 4. Adapted solution (creative technical workaround) 5. Outcome (success with cost, or failure leading to next problem)

Research Integration

For any hard SF thriller, verify:

• Current state of the technology/science
• Real-world analogues and case studies
• Institutional structures and jurisdictions
• Cost and timeline realities
• Legal and regulatory frameworks
• Industry economics and incentives
• Expert consensus and disagreements

Expert Consultation Prep

Effective questions for domain experts:

• What would accelerate [scenario] beyond current models?
• What's the realistic response timeline for [crisis]?
• How do national security/commercial concerns affect cooperation?
• What keeps you up at night about this area?
• What do outsiders always get wrong?

Common Hard SF Pitfalls

Thriller Craft Reference

Genre-specific guidance for spy thrillers and espionage fiction.

The Thriller Promise

Readers come to thrillers for:

• Tension: Something bad might happen at any moment
• Stakes: Important things are at risk
• Pace: Events move relentlessly forward
• Competence: Characters who are good at what they do
• Revelation: Secrets that reframe everything

Tension Architecture

The Ticking Clock

Every thriller needs time pressure. Examples:

• Hard deadline (summit, event, attack)
• Escalating threat intelligence
• Personal deadlines (relationship tensions, safety windows)

Information Management

Tension comes from what characters (and readers) know:

• Dramatic irony: Reader knows bomb location, characters don't
• Shared mystery: Neither reader nor character knows the mole's identity
• Character secrets: David knows things Grace doesn't (and vice versa)

Threat Escalation

Each act should increase: 1. What's at risk (personal → community → catastrophic) 2. How close the threat feels 3. How few options remain

Spy Thriller Specifics

Tradecraft Elements

Core espionage concepts to portray accurately:

Recruitment/Handling

• MICE motivations (Money, Ideology, Coercion, Ego)
• The pitch, the hook, the ongoing management
• Asset communication protocols

Cover

• Natural cover vs. official cover
• Cover for action vs. cover for status
• The "legend" (backstory) and maintaining it

Surveillance

• Detection (knowing you're watched)
• Counter-surveillance (verifying you're clean)
• Surveillance detection routes (SDRs)

Communication

• Dead drops, brush passes
• Signal sites
• Encrypted channels and their limitations

The Double Life Problem

Common in spy fiction—characters with multiple identities:

• Show the physical and emotional toll of compartmentalization
• Each identity should have its own "voice" and body language
• The seams where identities blur are the most interesting moments

Moral Complexity

Good spy fiction doesn't let protagonists off easy:

• Every "win" should cost something
• Necessary lies should damage relationships
• The "greater good" argument should be tested, not assumed

Example: Identity Conflict Thriller

Dual Identity Tension

Develop internal conflict through:

• Character using one identity's language/skills for another's purposes
• Genuine moments from one identity interrupted by demands of the other
• Secondary characters representing alternate paths
• Supporting characters as mirrors—others caught between worlds

Cultural Complexity

Background and setting should inform character dynamics:

• Character histories should inform their reactions and assumptions
• "Helping" narratives should be examined, not assumed
• Historical tensions can drive current distrust

Setting as Character

The setting should be specific enough to feel real:

• Specific neighborhoods and their characteristics
• Traffic patterns that affect plot timing
• Sensory palette: smells, sounds, atmosphere
• Social contrasts and tensions
• Community dynamics

Operational Realism

Balance authenticity with readability:

• Real tradecraft adds credibility
• But don't let procedure slow the story
• When in doubt, make it harder for protagonist, not easier

Scene-Level Thriller Craft

Opening Hooks

Each chapter should start with:

• Action in progress, or
• Immediate threat/tension, or
• Question that demands answer

Ending Hooks

Each chapter should end with:

• Cliffhanger (physical danger), or
• Revelation (information that reframes), or
• Decision point (character must choose), or
• Escalation (stakes just got higher)

Dialogue Under Pressure

Thriller dialogue should:

• Be clipped when tense
• Have subtext (what's not being said)
• Show competence through precision
• Allow for misinformation and deception

Action Sequences

• Short sentences, active verbs
• Specific physical details (not choreography lectures)
• Consequences (injuries matter, ammo runs out)
• Character decisions within the action
• Sensory chaos of real violence

Pacing Guidelines

Thriller Pacing Pattern

Not constant action—that's exhausting. Instead:

Tension → Action → Brief Recovery → Higher Tension → Bigger Action → Recovery...

Recovery Scenes

Use for:

• Character development
• Relationship moments
• Planting setup for later payoffs
• Letting reader catch breath before next escalation

The "Page-Turner" Test

Every 3-4 pages, something should:

• Change
• Reveal
• Threaten
• Decide

If more than 4 pages pass without one of these, look for cuts.

Common Thriller Mistakes

Research Verification

For spy thrillers, verify:

• Intelligence agency operations in your setting (general, not classified)
• Antagonist organization tactics and capabilities
• Local security forces and procedures
• Event security protocols relevant to plot
• Setting geography and logistics
• Community dynamics in your locations
• Technical capabilities (weapons, surveillance, etc.)