chapter-writing
This skill should be used when the user asks to "write a chapter", "next chapter", "chapter outline", "draft chapter", "continue the story", "write a scene",…
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.
$ npx -y skills add danjdewhurst/story-skills --skill plot-structure --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/plot-structureContext preview
The summary Claude sees to decide when to auto-load this skill.
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.
name: plot-structure description: 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.
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.
A story project must already exist (created via the story-init skill). Verify by checking for `story.md` in the project root.
1. Read `story.md` for genre and themes 2. Consult `references/structure-models.md` for available structures 3. Recommend a structure based on genre (default to three-act if unclear) 4. Update `plot/_index.md` frontmatter `structure` field 5. Populate the story structure section with the beat sheet 6. When CLI access is available, run `story validate .`
1. Read `story.md` for themes 2. Read `plot/_index.md` for existing arcs 3. Read `characters/_index.md` to understand available characters 4. Ask for:
5. Build the arc through conversation: setup, escalations, climax, resolution 6. Write the file using `references/arc-template.md` 7. Save to `plot/arcs/{arc-name-kebab}.md` 8. Update `plot/_index.md` arcs table 9. Update theme tracking in `plot/_index.md` 10. If characters are referenced, verify they exist in `characters/` 11. When CLI access is available, run `story reindex .`, `story links .`, and `story validate .`
Plot points live within arc files in the "Plot Points" table. When adding a plot point:
1. Read the relevant arc file 2. Add the plot point to the table with chapter reference (if known) 3. Add the event to `plot/timeline.md` in chronological order 4. If the plot point involves foreshadowing, add it to the arc's foreshadowing table 5. If the plot point creates a reader promise or mystery, create or update a record in `continuity/promises/` or `continuity/questions/` 6. When CLI access is available, run `story validate .`
The timeline at `plot/timeline.md` is a chronological master list of all story events across all arcs.
When adding events:
When reviewing the timeline:
Each arc tracks its own foreshadowing in the "Foreshadowing" table:
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`.
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.
Agent Skills for planning, tracking, and drafting fiction in markdown. Story Skills gives agents a shared project format for fiction: a story bible, character files, worldbuilding notes, factions, artifacts, plot arcs, scene state, continuity questions,
Repo: danjdewhurst/story-skills
This skill should be used when the user asks to "write a chapter", "next chapter", "chapter outline", "draft chapter", "continue the story", "write a scene",…
This skill should be used when the user asks to "create a character", "update a character", "add a character", "build a family tree", "character…
This skill should be used when the user asks to revise a chapter, edit prose, continuity check, find inconsistencies, audit character state, check timeline…
This skill should be used when the user asks to "start a new story", "initialize a story project", "create a story", "new book", "set up a story", or wants to…
This skill should be used when the user asks to validate, reindex, repair registries, check links, check continuity, count words, summarize a story project,…
This skill should be used when the user asks to "create a location", "add a location", "magic system", "political system", "build the world", "add culture",…