Table of Contents
Military sci-fi readers will eat you alive if your protagonist outranks a colonel by chapter three and salutes wrong. They know the difference between a battalion and a brigade. They notice when your dropship has the same loadout as a destroyer. The genre rewards research and punishes hand-waving, which is exactly why most writers either drown in spec sheets or skim past the parts that make mil-SF actually feel like mil-SF.
The fix is not more research. It is better infrastructure. Sudowrite's Story Bible, Worldbuilding cards, Describe, and Tone Shift give you a way to keep ranks consistent, tech plausible, and battle scenes fast without turning your novel into a Jane's Defence Weekly fan letter. Here is how to use them.
Why military sci-fi breaks most AI tools
General-purpose AI tools fail at mil-SF for three reasons. First, they default to vague pageantry. Ask a generic chatbot to write a boarding action and you get "the soldiers moved through the corridor with practiced precision." Second, they confuse military jargon across services. A Marine sergeant does not bark orders the same way a Navy chief does. Third, they cannot hold a complex chain of command across forty chapters without contradicting themselves by chapter twelve.
Sudowrite was built for fiction writers. The model that powers your prose, the persistent memory that tracks your tech, and the editing tools that tighten your battles are all tuned for narrative. Per the CX prose-modes matrix, sci-fi runs best on Claude 3 Opus through Write. It has the literary register mil-SF needs (think John Scalzi's Old Man's War, Linda Nagata's The Red, Marko Kloos's Frontlines) without sliding into textbook tone.
Build your tech and hierarchy in Worldbuilding cards first
Open Story Bible. Go to Worldbuilding. This is where you stop the contradiction problem before it starts.
Create a card for each piece of military tech your story relies on. Not every gun or grenade. The ones that matter to plot. A typical mil-SF novel needs maybe a dozen tech cards covering capital ships, dropships, infantry weapons, exo-suits, FTL drives, communications gear, and any signature weapon your protagonist carries. Each card should answer:
- What it is. One sentence. Class of ship, type of rifle, drive principle.
- What it can do. Range, payload, top speed, crew complement, fuel duration.
- What it cannot do. This is where most writers fail. A weapon without limits is not a weapon. It is a deus ex machina.
- Maintenance and failure modes. What breaks. How often. Who fixes it. Plot complications for free.
- Who uses it and who does not. Issued to fleet marines only? Outlawed by treaty? This is texture.
Then build hierarchy cards. One per faction. Marine Expeditionary Force, Colonial Defense Corps, Reaver Confederacy, whatever you have. List the rank structure top to bottom and specify how it differs from the others. When you write a scene where a Reaver captain orders a Colonial sergeant around, your Story Bible knows that is a violation of protocol. So will Chat when you ask it whether the scene tracks.
The card for a Reaver light cruiser might read: Talon-class corvette. 180-meter hull. Crew of forty-two. Two railgun batteries, six point-defense lasers, no torpedoes. Top sublight 0.04c. FTL via jury-rigged Concord drives, prone to misjumps. Cannot survive a direct frigate engagement. That one card stops you from writing a Talon-class doing torpedo runs in chapter seventeen.
Use Claude 3 Opus through Write for the prose
Once your cards are solid, switch your prose mode. Sudowrite's CX team recommends Claude 3 Opus for sci-fi work because it handles the genre's two competing demands. It can write hard technical detail without losing scene rhythm. It can also write a quiet moment between a sergeant and her squad mate without sounding like a procedural.
For mil-SF specifically, use Write in Guided mode more than Auto. Auto follows your story, which is great when the scene is clear. Guided lets you steer with direction like "the ambush goes wrong because the spotter mis-IDs the dropship class" or "the captain refuses the order without saying she refuses it." Mil-SF lives in those texture beats.
Push Creativity Dial to 4 or 5 for combat. Higher and your tactics start ignoring physics. Lower and your prose flattens. Bump it down to 2 or 3 for technical exposition where you need the AI to stick close to the specs in your cards.
Describe and Tone Shift for battle scenes
Battle scenes fail when they read like a play-by-play. Move, shoot, move, shoot, casualty, smoke. That is not a battle. That is a chess game with louder pieces.
What battle scenes need is sensory grounding. The way cordite smells different from plasma discharge. The vibration of a railgun through deck plating. The metallic taste in your mouth after concussive overpressure. The way silence sounds wrong when comm chatter cuts out. Describe pulls those details up across five senses so your battle stops being a sequence of events and becomes an experience.
Select the line where your soldier ducks behind cover. Run Describe. You get five separate sensory passes you can pull from. Pick the ones that fit your POV. Discard the rest.
The other half of battle prose is pacing. Mil-SF battles need short sentences. Fragments. Verbs front-loaded. Just the next thing. Then the next. Sudowrite's Tone Shift Fast-Paced does this surgically. Select a paragraph that reads slow, run Tone Shift, pick Fast-Paced. The tool cuts filter words, breaks long sentences, and pushes verb tense forward.
Use Ominous instead when you need the moment before contact, when the squad knows something is wrong but cannot say what. Use Conflicted when a character is doing something they hate doing. These tone tools are mode shifts, not rewrites of intent.
Mil-SF conventions checklist
Before you draft, walk through these. Most are unspoken rules that experienced mil-SF readers expect. Break them on purpose, not by accident.
- Ranks are consistent and earned. Promotions happen on-page or get explained in dialogue. Nobody jumps two ranks in a chapter without a reason.
- Logistics matter. Where does fuel come from. Who repairs the suits. Where do the rations show up. One line of this per chapter signals you know.
- Casualties have weight. Named characters die. Background characters die in larger numbers. Both should land.
- Tech has tradeoffs. The better the weapon, the harder it is to keep running. Mil-SF readers love constraints.
- Command friction is real. Your protagonist disagrees with orders sometimes. Other soldiers screw up. Communications fail. Intel is wrong.
- Civilians exist. Even on a warship someone is doing laundry. The war touches people who are not fighting it.
- POV stays disciplined. A grunt does not know the strategic picture. Use Sudowrite's per-chapter POV/Tense settings to keep this clean.
Battle scene before and after
Here is a draft passage most mil-SF writers produce on a first pass, then the version after Worldbuilding cards, Describe, and Tone Shift Fast-Paced.
Before:
Lieutenant Vega's squad moved through the corridor with practiced precision. The Reaver soldiers had set up a defensive position at the junction. Vega ordered her team to take cover. They began returning fire. The exchange of gunfire was intense. After several minutes of combat, the Reavers were defeated. Vega checked her squad for casualties. Corporal Walsh had been wounded in the shoulder but was still combat-effective. They continued toward the bridge.
Generic. Could be any war story. No tech texture. No sensory grounding. Pace is flat.
After:
Vega's squad pushed through corridor twelve. Bulkhead lights flickered red. The Reavers had locked down the cargo junction, three of them visible behind a hastily welded plate. One had a Talon-pattern railpistol. Wrong weapon for the range. He would burn through his magazine in eleven seconds.
"Walsh, smoke. Reyes, left lean. On my mark."
The smoke canister tasted like burnt copper through her filter. Vega's HUD flagged two Reaver heat signatures shifting position. She marked them. Reyes leaned. Fired. One signature went out.
The railpistol opened up. Walsh dropped, swearing. His shoulder plate sparked. Not penetrated. He kept his weapon up.
"Through," Vega said. They moved. The Reaver with the railpistol was already cycling his second magazine, hands shaking. He saw her coming. Did not raise the weapon in time.
The corridor smelled like ozone and lubricant. Walsh limped. They had eight minutes before the bridge realized this corridor was no longer Reaver-held.
That second version pulls on three things you set up before drafting. The Talon-pattern railpistol is in your Worldbuilding card as a short-range weapon that overheats. Vega's HUD and tactical thinking come from her Character card. The burnt-copper detail came from Describe. The clipped sentence rhythm is Tone Shift Fast-Paced.
Chapter Continuity and Chat keep your canon honest
Mil-SF readers are merciless about continuity. If your destroyer was at the Maranth Gate in chapter four and arrives at New Kepler in chapter five with no FTL transit mentioned, someone in your Discord will catch it. Worse, they will assume you do not respect them.
Sudowrite's Chapter Continuity check scans across chapters and flags contradictions. Use it after every two or three chapters, not just at the end. It will catch a rank you accidentally promoted someone to, a ship's crew complement that grew by twenty, a planet that orbits two different stars depending on which scene you wrote first.
Chat reads your Story Bible too. Once your Worldbuilding cards are solid, you can ask Chat questions like:
- "Would a Talon corvette realistically survive a fly-by from a Concord destroyer at three kilometers?"
- "Given the rank structure I set up for the Colonial Defense Corps, can a captain override a major in a planetside emergency?"
- "What would my squad lose if their primary comm relay went down at the start of chapter eight?"
Chat answers based on what you have actually built. Not based on Wikipedia and vibes. The more rigorous your Worldbuilding cards, the more useful Chat becomes as a tactical sparring partner.
Series Folder and Canvas for campaign-scale work
Mil-SF lives in series. Few writers stop at one book. The Frontlines series is eight novels. If you are planning a trilogy, you need shared canon across books.
Set up a Series Folder. Your Worldbuilding cards, faction rank structures, FTL rules, and tech specs all live there once. Each book inherits them. Update Vega's commission to Captain in book two and book three sees the change. This stops the most common series error: book one establishes a tech limitation, book three forgets it, and your reread audience riots.
Canvas helps you see the whole shape if your novel covers a campaign rather than a single engagement. Plot battles geographically. Track troop movements. Color-code chapters by which faction controls the system. You catch pacing problems early. You also catch the "my heroes have been on this planet for nine chapters" problem before your beta readers do. This works the way Brandon Sanderson maps his magic systems and GRRM maps his houses. You do not need to publish the map. You need to know it.
Muse versus Claude 3 Opus for mil-SF
Muse is Sudowrite's fiction-trained model and the default for romance, erotica, horror, and thriller per the CX matrix. It will not refuse explicit content and writes with novelist instincts. For mil-SF specifically, Claude 3 Opus through Write is the recommended pick because it handles hard sci-fi technical detail better. But if your mil-SF leans toward grimdark and visceral, like Joe Abercrombie crossed with Joe Haldeman, you may want to swap to Muse for the bleakest scenes. Test both. The Prose Modes matrix is a starting point, not a cage.
What to do before you write chapter one
Build twelve to fifteen Worldbuilding cards covering your major tech and hierarchy. Build Character cards for your squad with voice and rank notes. Set per-chapter POV/Tense. Pick Claude 3 Opus as your default prose mode. Set Creativity Dial to 4. Have Describe and Tone Shift in your muscle memory before you need them.
Now you can draft fast and know your continuity will hold. The mil-SF readers you want will notice. They are looking for writers who did the work. Sudowrite gives you the work without making you become a defense analyst to do it. Start worldbuilding free and see how far your campaign can run before chapter one is even written.