MCPInstall

story-architecture

Arc structure, narrative design, and pacing at multiple scales: saga, arc, chapter, scene. Use when structuring story at any level, planning arcs, designing chapter outlines, or evaluating whether narrative structure serves the story's goals.

Installs
477
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/haowjy/creative-writing-skills --skill story-architecture
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads story-architecture automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Story Architecture

Structure story at multiple levels so that each scene, chapter, and arc serves the larger narrative. The patterns here apply across methodologies (three-act, hero's journey, kishotenketsu, etc.): adapt them to what the story needs.

Structural Levels

Stories operate at nested scales. Decisions at one level constrain and enable decisions at others.

Saga/Series: the full story spanning multiple arcs. What's the overarching question or transformation? How do arcs build on each other?

Arc: a self-contained narrative movement spanning multiple chapters. Each arc has its own question, rising tension, and resolution, but also advances the saga-level story. An arc that resolves its own conflict but doesn't change anything at the saga level is filler.

Chapter: a unit of reading. Chapters need internal momentum (something changes by the end) and external momentum (the reader wants to continue).

Scene: the fundamental building block. A scene happens in a specific time and place, involves specific characters, and changes something. Scenes that don't change anything are candidates for cutting or combining.

What Makes Structure Work

Causation over sequence. "And then" is not structure. "Therefore" and "but" are. Events should cause or complicate each other, not merely follow each other. Can you reorder the scenes without the story breaking? If yes, the structure is a sequence, not a plot.

Stakes that escalate. Each structural level should raise the stakes from the previous one. Escalation doesn't always mean bigger explosions — stakes can escalate emotionally, morally, or informationally.

Setup and payoff. Every significant payoff needs setup, and every significant setup needs payoff. The best setups are invisible until the payoff arrives. Track open setups explicitly across arcs.

Tension and release. Sustained tension becomes numbness. The reader needs variation in intensity at every scale: within scenes, chapters, and arcs.

Resources

  • resources/arc-design.md: arc components (hook, complications, midpoint shift, crisis, resolution) and arc pacing.
  • resources/chapter-and-scene.md: chapter design (internal completeness, external pull), scene design (earning presence), outline vs discovery writing.
  • resources/structural-problems.md: common problems (saggy middle, rushed ending, filler arcs, disconnected scenes, stakes plateau) and when to use diagrams.

FAQ

What does the story-architecture skill do?

Arc structure, narrative design, and pacing at multiple scales: saga, arc, chapter, scene. Use when structuring story at any level, planning arcs, designing chapter outlines, or evaluating whether narrative structure serves the story's goals.

How do I install story-architecture?

Run npx skills add https://github.com/haowjy/creative-writing-skills --skill story-architecture in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/story-architecture/ (personal) or .claude/skills/story-architecture/ (project).

Which AI agents can use story-architecture?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is story-architecture safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains story-architecture?

It is published by haowjy in haowjy/creative-writing-skills. It has 477 recorded installs.

More from haowjy/creative-writing-skills

View all →

writing-principles

haowjy/creative-writing-skills

What fiction readers want (reader reward channels) and the specific ways LLM training damages them. Load when drafting prose, critiquing, or diagnosing why a passage feels flat.

Docs & Writing1K installs

creative-writing-craft

haowjy/creative-writing-skills

Craft references for writing fiction well: prose, scenes, style, voice, and genre/page-level technique. Load when a writer, critic, or muse needs how-to-write guidance rather than a production mode.

Docs & Writing788 installs

llm-writing

haowjy/creative-writing-skills

Load before writing or revising human-facing text. Choose words deliberately, ground the piece in the reader's context, and remove default LLM phrasing before the final draft.

Docs & Writing751 installs

writing-staffing

haowjy/creative-writing-skills

Dispatch reference for composing writing teams. Teaches which extra skills to attach, which files to pass, which resources to reference, and when to fan out versus run parallel lanes. Load when staffing a workflow.

Docs & Writing724 installs

story-review

haowjy/creative-writing-skills

Review work after prose exists: editorial review, craft critique, continuity/voice review, copyediting, proofreading, and synthesis of reader-sim signal. Load when diagnosing a draft rather than rewriting it.

story-planning

haowjy/creative-writing-skills

Planning work before prose: creative direction, story-planning, outlining, and story architecture. Load when deciding what should happen or how a story should be structured.

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.