Back to cookbook

AI Prompt to Develop a Character Arc From Flaw to Growth for Fiction Writing

0 views Updated

Make this prompt yours

Share

This character arc prompt helps fiction writers map out how a character changes over the course of a story, built for novelists and short story writers who have a character's surface traits figured out but aren't sure how that character should actually grow or break by the ending. Instead of vague notes like "she becomes braver," the prompt forces a concrete starting flaw, the specific pressure that exposes it, and a believable turning point.

The approach works by treating the arc as a cause-and-effect chain rather than a mood board: a core flaw or false belief, a series of events that test it, a moment where the old belief stops working, and a resolution that shows the change through action rather than narration. This keeps the arc grounded in plot events instead of floating as abstract character description that never shows up on the page.

If you're tracking this arc alongside a villain's arc, a subplot, or multiple POV characters across a longer manuscript, keeping the details consistent gets harder the longer the story runs, so it helps to write the full arc breakdown down in one place rather than relying on memory across drafts.

Prompt template

Make this prompt yours

prompt-template
331 tokens
You are a fiction writing coach helping develop a character arc for a novel or short story. CONTEXT: Character name: [NAME] Current personality/role: [BRIEF DESCRIPTION] Starting flaw or false belief: [WHAT THEY WRONGLY BELIEVE OR STRUGGLE WITH] Genre/tone: [GENRE] Story length: [SHORT STORY / NOVEL - APPROX WORD COUNT OR CHAPTER COUNT] Ending state (if known): [WHAT YOU WANT THEM TO BECOME, OR LEAVE BLANK] TASK: 1. State the character's core flaw as a specific false belief, not a vague trait. 2. Identify the originating wound or event that created this belief. 3. Propose 3 escalating plot events that each test this belief, with the final one causing it to visibly fail. 4. Describe the turning point: the specific choice or action that marks the shift away from the old belief. 5. Describe how the resolution should be shown through action or dialogue in the climax, not stated outright. 6. Note one way a secondary character's reaction to this character should change from story-start to story-end. CONSTRAINTS: - Do not resolve the arc through an internal monologue alone; the change must show up in a decision or action. - Keep the flaw specific enough to drive concrete scenes, not a one-word trait. - Flag if the proposed ending state feels like too large a jump from the starting flaw given the story length provided. OUTPUT FORMAT: Return as: Core Flaw, Originating Wound, Testing Events (3), Turning Point, Resolution (how shown), Secondary Character Shift.

Want it sharper? Optimize this prompt with Prompt Optimizer, check it with the Prompt Debugger or shorten it with the Token Optimizer.

Example input

example-input
95 tokens
Character name: Mara Okafor Current personality/role: A field surgeon who refuses to delegate any decision to her junior staff Starting flaw or false belief: She believes that if she isn't personally controlling every outcome, people under her care will die, because she failed to save a patient early in her career after trusting someone else's judgment Genre/tone: Literary fiction, hospital drama Story length: Novel, roughly 90,000 words Ending state: Leave blank

When to use it

  • You know a character's personality but can't explain how or why they change by the end of the story
  • Beta readers say a character's growth feels sudden or unearned
  • You're outlining a novel and need each major character's arc to intersect with specific plot beats
  • You're revising a draft and suspect a character's arc flattens out in the middle act

Best practices

  • Tie the character's flaw to a specific past event or belief, not just a personality label like "stubborn"
  • Make the midpoint test fail in a way that's directly caused by the flaw, not by bad luck
  • Show the change through a decision or action in the climax, not through a character stating they've changed
  • Check that secondary characters react differently to the character before and after the arc completes

Common mistakes

  • Writing a flaw that's really just a quirk, with no real stakes attached to keeping or losing it
  • Resolving the arc through an internal realization the reader is told about rather than shown
  • Giving the character a complete personality transplant instead of a believable, partial shift
  • Forgetting to make other characters or the plot react to the change, so it has no visible consequences

FAQs

What is a character arc in fiction writing?

A character arc is the change a character undergoes over the course of a story, usually moving from a flawed belief or behavior toward a different way of seeing or acting, shown through specific decisions rather than stated directly.

How do I know if my character's arc feels earned instead of sudden?

An earned arc usually has at least two or three escalating events that test the character's flaw before the turning point, so the change is a result of pressure rather than a single convenient realization.

Should every character in a novel have a complete arc?

No, usually only the protagonist and a few major characters need a full arc; minor characters can stay static or serve a single narrative function without needing their own transformation.

Which Cuelara tool can help me turn these arc notes into a full writing prompt?

Prompt Builder — it turns a plain description, like the arc notes above, into a complete structured prompt you can hand to ChatGPT, Claude, or Gemini for drafting actual scenes.

Found this prompt useful? Share it.

Share

More in Creative Writing

Creative Writing

AI Prompt to Track Beta Reader Feedback on a Manuscript via Google Workspace's MCP Server

This AI prompt helps novelists, screenwriters, and serial fiction writers turn scattered beta reader comments into one organized revision lo…

Role: You are a developmental editing assistant helping a fiction writer process beta reader feedback.

Context:
- Manuscript title: [MANUSCRIPT_TITLE]
- Genre: [GENRE]
- Draft version this feedback applies to: [DRAFT_VERSION]
- Number of beta readers: [NUMBER_OF_BETA_READERS]
- Feedback sources: [GOOGLE_DOCS_LINKS_OR_SHEET_TRACKER]
- Chapters covered: [CHAPTER_LIST_OR_RANGE]

Task:
1. Read every comment and feedback row tied to the chapters listed above.
2. Group the feedback by chapter, then by theme: pacing, character motivation, plot logic, continuity, prose style.
3. For each theme, note how many distinct readers raised it and quote the specific line or scene it refers to.
4. Separate feedback into two tiers: "Structural - likely needs a rewrite" (raised by 2+ readers or affects plot logic/continuity) and "Style preference - optional" (raised by one reader and purely about taste).
5. For each structural item, suggest one concrete next step for the revision.

Constraints:
- Do not merge feedback from different chapters into one item.
- Do not discard or downplay a single reader's note if it points to a factual continuity error, even if only one person caught it.
- Keep each item to 2-3 sentences.

Output format:
For each chapter, output:
Chapter: [name/number]
Structural issues (reader count, quote, suggested fix)
Style preferences (reader, quote)
End with a short "Top 3 priorities across the manuscript" list.

Make this prompt yours

Creative Writing

AI Prompt to Build a Fantasy World-Building Bible for Your Novel

This world building prompt is built for fantasy and sci fi writers who have a setting idea in their head but nothing written down in a consi…

ROLE: You are a worldbuilding consultant helping a novelist develop a consistent fictional setting.

CONTEXT:
- Genre: [FANTASY / SCI-FI / OTHER]
- Core premise: [ONE OR TWO SENTENCES ON THE CENTRAL STORY IDEA]
- Existing ideas to build from: [ANY NAMES, PLACES, OR RULES ALREADY DECIDED]
- Tone of the world: [e.g. grim and political / lighthearted and adventurous]
- Scope needed: [NOVEL-LENGTH SERIES / SINGLE BOOK / RPG CAMPAIGN]

CONSTRAINTS:
- Define the magic or technology system's rules and limits before any other section
- Keep every later section consistent with those rules; flag anything that would contradict them
- Use consistent spelling for all invented names and terms throughout
- Do not introduce real-world political or religious references as direct analogues

OUTPUT FORMAT:
1. World overview (3-4 sentences)
2. Magic/technology system: core rule, limits, and cost of use
3. Geography: 3-5 key locations with one paragraph each
4. Factions: 2-4 groups with their goals and relationship to each other
5. Glossary: invented terms and names with one-line definitions

Build the world bible now using the information above.

Make this prompt yours

Creative Writing

AI Prompt to Build and Maintain a Fiction Story Bible Using Airtable's MCP Server

This AI prompt is built for novelists, screenwriters, and fiction writers who want to keep their story bible — characters, locations, timeli…

ROLE: You are a story bible assistant with access to an Airtable base via MCP. Your job is to extract structured details from the writing I give you and propose records for my existing tables.

CONTEXT:
- Base name: [BASE NAME]
- Tables and key fields:
  - Characters: [FIELD LIST, e.g. Name, Role, Traits, Arc Status, First Appearance]
  - Locations: [FIELD LIST]
  - Timeline: [FIELD LIST, e.g. Event, Chapter, Characters Involved, Date/Order]
- Source material: [PASTE CHAPTER TEXT, SCENE SUMMARY, OR EXISTING NOTES]

TASK:
1. Read the source material and identify every character, location, and timeline event mentioned.
2. For each one, check whether it likely already exists in the base (use name matching) or is new.
3. Propose a record for each: list the table, the fields, and the values you would fill in.
4. Flag anything ambiguous (unclear relationship, conflicting detail, uncertain spelling of a name) instead of guessing.

CONSTRAINTS:
- Do not write to the Airtable base until I explicitly confirm the proposed list.
- Do not invent details that are not stated or strongly implied in the source material.
- Keep character and location names consistent with how they appear in [EXISTING REFERENCE LIST, IF ANY].

OUTPUT FORMAT:
- A numbered list grouped by table (Characters, Locations, Timeline)
- Each entry: proposed field values in a simple key: value format
- A final "Needs Review" section listing anything flagged as ambiguous

After I confirm, create or update the corresponding Airtable records using the MCP connection and confirm back to me which records were written.

Make this prompt yours