agentleFS
RandomNestRandomNest/aivideo-production-skills/skills/story-architect/SKILL.md

story-architect

Skill15 starsChanged 9 months agoMITView on GitHub

Use when defining a new story, expanding a premise into structured beats, or when narrative direction feels unclear. Trigger when the user mentions "outline," "beat sheet," "structure," "act breakdown," "story arc," or "scene list.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when:

    line 22
  2. Distinctive:

    Do NOT use for scene polish or dialogue tuning.

    line 31
  3. Distinctive:

    If project context exists (character list, theme, genre), review it.

    line 39
  4. Distinctive:

    If prior scenes exist, ensure continuity alignment.

    line 40
  5. Distinctive:

    Ensure climax resolves core tension.

    line 90
  6. Distinctive:

    Verify each scene changes state.

    line 92
  7. Distinctive:

    Avoid deus ex machina resolution.

    line 110

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Role

You are a narrative architect responsible for structural integrity before production begins.

Your goal is to create a story that scales — not just a sequence of scenes.

You must prevent structural weakness, artificial escalation, and directionless storytelling.


When To Use

Use this skill when:

  • A project begins from a premise or logline
  • The user requests an outline or structure
  • Scenes feel disconnected
  • Stakes feel flat
  • Escalation is unclear
  • A rewrite requires structural re-evaluation

Do NOT use for scene polish or dialogue tuning.


Context Requirements

Before proceeding:

  1. If project context exists (character list, theme, genre), review it.
  2. If prior scenes exist, ensure continuity alignment.
  3. Confirm intended format:
    • Short film
    • Feature
    • Episodic
    • Series arc

Required Inputs

  • Logline or premise
  • Genre
  • Tone
  • Intended length (short / feature / episode)
  • Optional: Theme statement
  • Optional: Character list

Required Artifacts

1. BEATS_v###.md

Must include:

  • Inciting incident
  • Escalation sequence
  • Midpoint shift
  • Crisis
  • Climax
  • Resolution

2. SCENES_v###.csv

Each scene must define:

  • scene_id
  • summary
  • goal
  • conflict
  • outcome
  • location
  • time_of_day
  • characters_present

Process

  1. Define central dramatic question.
  2. Identify protagonist objective.
  3. Map escalation ladder.
  4. Define irreversible midpoint shift.
  5. Ensure climax resolves core tension.
  6. Translate beats into scene units.
  7. Verify each scene changes state.

Structural Evaluation Checklist

Every scene must:

  • Contain a clear goal.
  • Contain resistance or obstacle.
  • Produce a state change.
  • Escalate stakes relative to prior scenes.

The overall arc must:

  • Increase tension across acts.
  • Avoid repetitive stakes.
  • Resolve central question.
  • Avoid deus ex machina resolution.

Gate Behavior

FAIL if:

  • Any scene lacks defined goal/conflict/outcome.
  • Stakes do not escalate across the narrative.
  • The midpoint does not meaningfully alter trajectory.
  • The climax does not resolve the central dramatic question.

PASS when:

  • Narrative spine is clear.
  • Escalation is cumulative.
  • Character decisions drive progression.
  • Structure can support 50+ scenes without collapse.

Escalation Policy

Escalate to Judgment Tier if:

  • Structural uncertainty remains after revision.
  • Multiple alternative arcs compete.
  • Stakes feel conceptually weak.
  • The theme is unclear.

Common Failure Modes

  • Episodic events without escalation.
  • Artificial conflict injected without causality.
  • Passive protagonist.
  • Repetitive tension pattern.
  • Climax not tied to central question.
  • Resolution through coincidence.

Related Skills

  • script-breakdown
  • character-psychology
  • narrative-red-team
  • audience-simulator

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.