Plot Structure
Overview
Plan and manage story arcs, plot points, foreshadowing, and narrative timeline. Each arc is a markdown file in plot/arcs/ with a chronological timeline maintained in plot/timeline.md. The plot index tracks all arcs, their status, and theme coverage.
Prerequisites
A story project must already exist (created via the story-init skill). Verify by checking for story.md in the project root.
Choosing a Story Structure
- Read
story.md for genre and themes
- Consult
references/structure-models.md for available structures
- Recommend a structure based on genre (default to three-act if unclear)
- Update
plot/_index.md frontmatter structure field
- Populate the story structure section with the beat sheet
- When CLI access is available, run
story validate .
Creating an Arc
- Read
story.md for themes
- Read
plot/_index.md for existing arcs
- Read
characters/_index.md to understand available characters
- Ask for:
- Arc name
- Type (main, subplot, character, thematic)
- Which characters are involved
- Which themes it serves
- Build the arc through conversation: setup, escalations, climax, resolution
- Write the file using
references/arc-template.md
- Save to
plot/arcs/{arc-name-kebab}.md
- Update
plot/_index.md arcs table
- Update theme tracking in
plot/_index.md
- If characters are referenced, verify they exist in
characters/
- When CLI access is available, run
story reindex ., story links ., and story validate .
Managing Plot Points
Plot points live within arc files in the "Plot Points" table. When adding a plot point:
- Read the relevant arc file
- Add the plot point to the table with chapter reference (if known)
- Add the event to
plot/timeline.md in chronological order
- If the plot point involves foreshadowing, add it to the arc's foreshadowing table
- If the plot point creates a reader promise or mystery, create or update a record in
continuity/promises/ or continuity/questions/
- When CLI access is available, run
story validate .
Timeline Management
The timeline at plot/timeline.md is a chronological master list of all story events across all arcs.
When adding events:
- Insert in chronological order
- Link to the relevant arc and chapter
- Keep entries concise (one line per event)
When reviewing the timeline:
- Check for chronological consistency
- Identify pacing issues (too many events clustered, long gaps)
- Flag arcs that haven't progressed
Foreshadowing Tracking
Each arc tracks its own foreshadowing in the "Foreshadowing" table:
- Planted: What hint or setup is placed
- Payoff: What the payoff will be
- Chapter Planted / Chapter Payoff: Where each occurs
- Status:
planned, planted, or paid-off
During chapter writing, flag any planted items that haven't been paid off as reminders.
For durable cross-arc setup/payoff tracking, also maintain continuity/promises/{promise-kebab}.md with status, planted, payoff, arcs, and characters. For mystery or open-continuity tracking, maintain continuity/questions/{question-kebab}.md.
Cross-Referencing
- Arcs reference characters via frontmatter
characters field
- Arcs reference themes via frontmatter
themes field
- Plot points reference chapters
- Timeline entries link arcs and chapters
- Theme tracking in
plot/_index.md maps themes to arcs and chapters
- Promises and questions reference chapters, arcs, and characters where relevant
CLI Maintenance
Use the Story CLI when it is available. If story is not installed but the story-maintenance skill is present, use node ../story-maintenance/scripts/story.js with the same arguments, resolving the path relative to this skill folder. If no CLI is available, perform the registry and backlink checks manually.
Reference Files
references/arc-template.md - Template for arc files with frontmatter and sections
references/question-template.md - Template for continuity questions and mysteries
references/promise-template.md - Template for setup/payoff tracking
references/structure-models.md - Story structure models (three-act, hero's journey, save the cat, kishotenketsu, five-act) with beat sheets
1---
2name: plot-structure
3description: This skill should be used when the user asks to "create a plot arc", "story structure", "add a plot point", "story timeline", "track foreshadowing", "pacing", "act structure", "story arc", "plot outline", or wants to plan and manage the narrative structure of a story.
4metadata:
5 source: https://skillmd.com/skills/danjdewhurst/plot-structure
6---
7
8# Plot Structure
9
10## Overview
11
12Plan and manage story arcs, plot points, foreshadowing, and narrative timeline. Each arc is a markdown file in `plot/arcs/` with a chronological timeline maintained in `plot/timeline.md`. The plot index tracks all arcs, their status, and theme coverage.
13
14## Prerequisites
15
16A story project must already exist (created via the story-init skill). Verify by checking for `story.md` in the project root.
17
18## Choosing a Story Structure
19
201. Read `story.md` for genre and themes
212. Consult `references/structure-models.md` for available structures
223. Recommend a structure based on genre (default to three-act if unclear)
234. Update `plot/_index.md` frontmatter `structure` field
245. Populate the story structure section with the beat sheet
256. When CLI access is available, run `story validate .`
26
27## Creating an Arc
28
291. Read `story.md` for themes
302. Read `plot/_index.md` for existing arcs
313. Read `characters/_index.md` to understand available characters
324. Ask for:
33 - Arc name
34 - Type (main, subplot, character, thematic)
35 - Which characters are involved
36 - Which themes it serves
375. Build the arc through conversation: setup, escalations, climax, resolution
386. Write the file using `references/arc-template.md`
397. Save to `plot/arcs/{arc-name-kebab}.md`
408. Update `plot/_index.md` arcs table
419. Update theme tracking in `plot/_index.md`
4210. If characters are referenced, verify they exist in `characters/`
4311. When CLI access is available, run `story reindex .`, `story links .`, and `story validate .`
44
45## Managing Plot Points
46
47Plot points live within arc files in the "Plot Points" table. When adding a plot point:
48
491. Read the relevant arc file
502. Add the plot point to the table with chapter reference (if known)
513. Add the event to `plot/timeline.md` in chronological order
524. If the plot point involves foreshadowing, add it to the arc's foreshadowing table
535. If the plot point creates a reader promise or mystery, create or update a record in `continuity/promises/` or `continuity/questions/`
546. When CLI access is available, run `story validate .`
55
56## Timeline Management
57
58The timeline at `plot/timeline.md` is a chronological master list of all story events across all arcs.
59
60When adding events:
61- Insert in chronological order
62- Link to the relevant arc and chapter
63- Keep entries concise (one line per event)
64
65When reviewing the timeline:
66- Check for chronological consistency
67- Identify pacing issues (too many events clustered, long gaps)
68- Flag arcs that haven't progressed
69
70## Foreshadowing Tracking
71
72Each arc tracks its own foreshadowing in the "Foreshadowing" table:
73- **Planted:** What hint or setup is placed
74- **Payoff:** What the payoff will be
75- **Chapter Planted / Chapter Payoff:** Where each occurs
76- **Status:** `planned`, `planted`, or `paid-off`
77
78During chapter writing, flag any `planted` items that haven't been paid off as reminders.
79
80For durable cross-arc setup/payoff tracking, also maintain `continuity/promises/{promise-kebab}.md` with `status`, `planted`, `payoff`, `arcs`, and `characters`. For mystery or open-continuity tracking, maintain `continuity/questions/{question-kebab}.md`.
81
82## Cross-Referencing
83
84- Arcs reference characters via frontmatter `characters` field
85- Arcs reference themes via frontmatter `themes` field
86- Plot points reference chapters
87- Timeline entries link arcs and chapters
88- Theme tracking in `plot/_index.md` maps themes to arcs and chapters
89- Promises and questions reference chapters, arcs, and characters where relevant
90
91## CLI Maintenance
92
93Use the Story CLI when it is available. If `story` is not installed but the `story-maintenance` skill is present, use `node ../story-maintenance/scripts/story.js` with the same arguments, resolving the path relative to this skill folder. If no CLI is available, perform the registry and backlink checks manually.
94
95## Reference Files
96
97- **`references/arc-template.md`** - Template for arc files with frontmatter and sections
98- **`references/question-template.md`** - Template for continuity questions and mysteries
99- **`references/promise-template.md`** - Template for setup/payoff tracking
100- **`references/structure-models.md`** - Story structure models (three-act, hero's journey, save the cat, kishotenketsu, five-act) with beat sheets