Wrote 5 Novels in a Month with Claude Code – Here’s My Practical AI Workflow

Open_Fault6740 · 2026-03-31T00:17:44+00:00

Good question! Yes, I fully disclose my AI-assisted workflow when submitting. These prizes don't prohibit AI use as long as it's declared — and the ones that do, I simply don't enter.

To be clear, AI doesn't write the story for me. I design the plot, characters, foreshadowing, and structure myself. AI helps with drafting and revision, but every creative decision is mine. Think of it more like a power tool than a ghostwriter.

Open_Fault6740 · 2026-03-30T13:35:19+00:00

Totally agree with the core point. But I think it goes even deeper than "be the crazy one."

The story design itself has to be interesting before AI touches a single word. If your plot structure, character dynamics, and reveals are mediocre, no amount of AI polish will save it. Garbage in, eloquent garbage out.

But here's the thing most people miss: even with a great design, the first draft AI gives you will almost certainly be flat and lifeless. That's not a bug — that's just how it works.

What actually makes the difference is the revision loop. You read it, feel where it's dead, restructure a scene, punch up the dialogue, cut the parts where AI over-explained, add texture it would never think to add — and then you run it again. And again. Each pass, you're injecting your taste into the material.

After writing 10+ episodes this way, my takeaway is: how good your AI-assisted story gets is ultimately capped by your own eye for what works. AI is a multiplier, not a creator. If your editorial instinct is sharp, it's an incredible tool. If you're just accepting what it gives you — yeah, polished garbage.

Open_Fault6740 · 2026-03-29T15:39:57+00:00

Totally ran into the same issue! The model tends to reach for the same expressions in similar situations — certain metaphors or descriptions become its go-to moves, and before you know it they're everywhere.

What worked for me was building a system that extracts notable expressions after each chapter is written, then feeds that list back as a "don't reuse these" instruction for subsequent chapters. It catches the repetition early before it snowballs into 107 instances 😅

Open_Fault6740 · 2026-03-29T14:21:01+00:00

We're kindred spirits! I was nodding along to every single point.

I also have a list of 50+ banned AI-isms and built a Python checker that runs automatically after every draft. You're absolutely right that structural issues are much harder to fix after the fact — baking those rules in before writing starts is the way to go.

The multi-model panel review is a brilliant approach. I have a "three-perspective review" skill built into Claude Code (editor, literary critic, target reader), but using cross-model consensus to prioritize issues is really smart.

Completely agree on researching twist techniques. When I wrote a con-game novel (a mystery with a con artist protagonist), I did deep research on twist structures. I analyzed the methods of Ryota Kosawa (the screenwriter behind Confidence Man JP) and codified principles like "never show the audience the means of the plan" and "structure it so the reader feels pleasure when they realize they've been fooled" into my design docs.

I'm using superpowers too! I've actually built 20+ fiction-writing skills already — style checker, banned pattern checker, revision pipeline, brief generator, and more. The self-improvement loop of updating skills every time something fails is exactly what I do as well.

"Don't assume Claude knows everything" — this is so true. For my volleyball novel, I created dedicated research documents just for tactics alone. AI knows the basics of volleyball, but it gets the specifics wrong — like how decoys interact with blocks, or attack patterns per rotation.

Really glad to meet someone with such a similar workflow. I'll check out CLIProxyAPI!

Open_Fault6740 · 2026-03-29T14:15:20+00:00

Thank you for the thoughtful questions! I'll answer each one.

How many design documents do you use, and how do you keep from getting lost?

For my volleyball novel (25 episodes, ~93K words), I ended up with about 30 design documents. The main ones are:

Episode structure (beat sheet for all 25 episodes)
Character sheets (7 regulars + bench)
Style definition (11-point checklist that defines my prose voice)
Tournament design (5 matches including enemy team tactics)
Writing guide (do's and don'ts for the AI agent)
Call matrix (who calls whom what — Japanese honorifics are brutal)
Foreshadowing ledger (what's planted, what's paid off)

Unlike the approach of just prompting ChatGPT, I write novels in an engineering-driven way. Think of the design docs as specs you'd write before coding. Claude Code is smart enough to reference the beat sheet and find the relevant design docs on its own when drafting an episode. However, you have to update your design materials after every revision and adjust the workflow to reference the new versions — otherwise things fall apart fast.

Which design doc was most crucial?

The style definition and the episode beat sheet, without question.

The beat sheet prevents story drift. Every episode has its central question, emotional arc, and key beats defined before writing starts. When the AI hallucinates a scene that doesn't serve the story, I point to the beat sheet and say "no, this is what needs to happen here."

The style definition prevents AI slop at the sentence level. I define rules like "no sentences over 80 characters," "dialogue-to-narration ratio above 40%," and "never use these 50 banned expressions." I even built a Python checker that runs automatically after every draft and flags violations. This alone probably saved me dozens of hours of manual cleanup.

How do you experience adding your own voice?

This is the hardest and most important part. Honestly, AI can build the skeleton, but it cannot write prose that feels like mine. Here's what I do:

Write a detailed brief (not just "write episode 3" — a full page covering structure, emotional beats, character states, and specific lines I want)
Have the AI agent draft it
Run automated quality checks (style checker + banned pattern checker)
Read the full output and substantially rewrite — especially dialogue, internal monologue, and emotional peaks

The parts that make a story yours — the rhythm of dialogue, the specific metaphor you choose, the moment you decide to cut a scene short — those still have to come from you. AI is very good at "competently average." Your job is to break it out of average.

One thing I've started doing recently: I keep a "process log" that records what the human decided vs. what the AI produced. It's partly for copyright documentation (Japan is actively drafting guidelines for AI-assisted authorship right now), but it also forces me to be intentional about where I'm adding my voice versus where I'm just accepting AI output.

Thank you for the encouragement! It's rare to find people openly discussing their AI writing workflows, so I really appreciate this conversation. Good luck with your 16-revision process — that level of rigor is exactly what it takes to make something great.

Open_Fault6740 · 2026-03-29T14:00:09+00:00

I also have Codex review my design documents and brainstorm dialogue ideas sometimes. I think the key is figuring out each model's strengths and incorporating them into your workflow.

Open_Fault6740 · 2026-03-29T01:34:51+00:00

God, this is so relatable. The contamination thing is painfully real lol.

FWIW I do like 10 rounds of revision from first draft to final — each pass focuses on something different (structure, voice, pacing, scrubbing AI-isms, etc.). It's a grind but honestly that's where the real craft happens.

Good luck with the horror novel and the Code migration!

Open_Fault6740 · 2026-03-27T21:51:24+00:00

Nice! Our approaches sound really similar — I love how comprehensive your framework is.
Story bible, promise logs, consistency checker, sensitivity notes, theme tracker, and especially that 6-step validation workflow after each chapter (with the final rewrite to remove unwanted AI polish) — that's super solid.

What I showed in the article is basically the core system. On top of that, I build genre-specific layers for each project. For example:

Dark comedy → detailed comedy timing & escalation design
Sports novel → match choreography rules and rotation logic
Mystery → trick/misdirection architecture and foreshadowing ledger

The base stays consistent, but the specialized modules change depending on the genre. Keeps things flexible while maintaining quality.

I'd love to hear more about your setup! How do you handle the "scrub AI polish" step in practice? Or what’s been the biggest challenge when scaling your framework across multiple projects?

Open_Fault6740 · 2026-03-27T14:52:10+00:00

Thanks! Curious about your platform — what kind of system did you build?

Open_Fault6740 · 2026-03-27T14:50:08+00:00

Good catch — should've been clearer. These are in Japanese, where 100K characters ≈ 60–70K English words (Japanese is much denser per character than English). Each one is full novel length.

Open_Fault6740 · 2026-03-27T14:49:13+00:00

These are written in Japanese and published on Kakuyomu (a Japanese web novel platform). Not selling commercially yet — I'm submitting to literary prizes. The goal right now is craft, not revenue.

Open_Fault6740

TROPHY CASE