Story Idea Developer

A creative writing skill that transforms rough seed ideas into fully developed story outlines complete with plot structure, character arcs, world-building details, and chapter-by-chapter breakdowns. Supports multi-platform export to Scrivener, Google Docs, Notion, and writing software for seamless integration into your drafting workflow.

Supported Platforms & Integrations

Platform	Integration Type	Features
Scrivener	OPML / Markdown Export	Chapter structure, character sheets, research folders
Google Docs	Export	Formatted outline documents with section headings
Notion	Markdown / Database	Story bibles, character databases, plot timeline boards
Obsidian	Markdown + Links	Interconnected world-building wikis with backlinks
Campfire	Export	Character profiles, world maps, timeline entries
Plottr	Structure Export	Visual plot timelines with character thread tracking

When to Use This Skill

• Use this when you have a single-sentence story idea and need to develop it into a full outline

• Use this when you have characters but no plot, or a plot but no compelling characters

• Use this when you need to structure a novel with proper three-act or five-act architecture

• Use this when world-building for fantasy or sci-fi and need consistent internal logic

• Use this when you are stuck in the middle of a draft and need to re-outline from your current position

• Use this when preparing for NaNoWriMo and need a complete chapter-by-chapter roadmap

• Consider alternatives when you need line-level prose editing or style feedback

• Consider alternatives when you want AI to write the actual draft rather than the outline

• Consider alternatives when you need genre-specific market analysis or publishing advice

Quick Start

Copy
# .claude/skills/story-idea-developer.yml
name: Story Idea Developer
trigger: "develop story"
context:
  genre: literary-fiction
  structure: three-act
  target_length: novel
  detail_level: detailed

First Run Example:

User: Develop this idea: A retired astronaut discovers that 
memories from her last mission are being slowly replaced 
with someone else's.

Expected Output:

## Story Development: "Borrowed Light"
Genre: Psychological Sci-Fi / Literary Fiction
Target: Novel (80,000-90,000 words)

### Core Premise
Dr. Elena Vasquez, 62, retired from NASA after a classified 
solo mission to a decommissioned space station. Three years 
later, she notices her memories of the mission shifting — 
small details first, then entire conversations she never 
had. The replacing memories belong to Yuki Tanaka, a 
Japanese astronaut who died on that same station in 2019.

### Theme
Identity persistence — are we our memories, or something 
deeper? What happens when the boundary between self and 
other dissolves?

### Three-Act Structure
**Act I (Ch 1-8):** Elena notices discrepancies...
**Act II (Ch 9-20):** Investigation reveals...
**Act III (Ch 21-26):** Confrontation with...

Advanced Configuration

Platform-Specific Setup:

Copy
# Scrivener project structure
scrivener:
  project_template: novel
  include_character_sheets: true
  research_folder: true
  compile_format: manuscript

# Obsidian world-building wiki
obsidian:
  vault_path: ~/Documents/Writing/WorldBuilding
  character_template: templates/character.md
  location_template: templates/location.md
  timeline_plugin: true

Parameter	Type	Default	Description
genre	string	literary-fiction	literary-fiction, fantasy, sci-fi, thriller, romance, horror, mystery
structure	string	three-act	three-act, five-act, heros-journey, save-the-cat, kishoetenketsu
target_length	string	novel	short-story, novella, novel, series
detail_level	string	detailed	brief, standard, detailed, exhaustive
pov	string	third-limited	first, third-limited, third-omniscient, second, multiple
tone	string	serious	serious, humorous, dark, whimsical, literary
character_depth	int	3	1 (sketch) to 5 (full psychological profile)
world_building	bool	true	Include world-building details and internal rules
chapter_breakdown	bool	true	Generate chapter-by-chapter outline
subplot_count	int	2	Number of subplots to weave into main narrative
conflict_layers	int	3	Internal, interpersonal, and external conflict depth

Core Concepts

Concept	Description
Seed Expansion	Transforms a single-sentence idea into premise, theme, and conflict layers
Character Web	Maps relationships, motivations, and arc trajectories for all major characters
Plot Architecture	Applies proven narrative structures with customizable act and beat placement
World Consistency	Ensures internal rules of the story world remain logically coherent
Tension Mapping	Charts rising and falling tension across chapters to maintain reader engagement

+------------------+     +------------------+     +------------------+
|  Seed Idea       |---->|  Premise Engine  |---->|  Character Web   |
|  (one sentence   |     |  (theme, genre,  |     |  (profiles, arcs,|
|   concept)       |     |   core conflict) |     |   relationships) |
+------------------+     +------------------+     +------------------+
                                                          |
                                                          v
+------------------+     +------------------+     +------------------+
|  Export Format   |<----|  Chapter Outline |<----|  Plot Structure  |
|  (Scrivener,     |     |  (scene-by-scene |     |  (acts, beats,   |
|   Notion, etc.)  |     |   breakdown)     |     |   tension curve) |
+------------------+     +------------------+     +------------------+

Workflow Examples

Scenario 1: Fantasy Novel from Character Concept

Input: "A blacksmith who can forge weapons that absorb the 
wielder's fears — but each weapon takes a year off her life"

Output:
## Character-Driven Development

**Protagonist:** Seren Ashvale, 34, village blacksmith
- Fatal flaw: Cannot say no to those in need
- Internal conflict: Self-sacrifice vs self-preservation
- Arc: Learns that true strength is refusing to destroy 
  herself for others' battles

**World Rules:**
- Fear-forging requires empathic resonance with client
- Weapons are sentient, carrying echoes of absorbed fears
- Life-cost is visible: hair grays, skin thins
[Full outline follows with 30 chapter breakdowns]

Scenario 2: Short Story for Literary Magazine

Input: "Develop a 5,000-word literary short story about 
a translator who realizes the language she's translating 
is changing her personality."

Output:
## Short Story Outline: "Loanwords"
Target: 5,000 words (literary magazine submission)

**Structure:** Four sections mirroring language acquisition
1. Recognition (1,200 words) — first personality shift
2. Immersion (1,500 words) — deepening changes
3. Fluency (1,300 words) — loss of original self
4. Translation (1,000 words) — finding hybrid identity

Scenario 3: Mystery Series Arc

Input: "Plan a 4-book cozy mystery series set in a 
botanical garden with a retired botanist detective."

Output:
## Series Arc: "The Thornwood Mysteries"

**Series-Level Arc:** Dr. Iris Blackwood uncovers a 
40-year-old conspiracy connected to her mentor's research

**Book 1:** "Deadly Nightshade" — poisoning at annual gala
**Book 2:** "Root System" — skeleton in greenhouse foundation
**Book 3:** "Cross-Pollination" — rival garden sabotage
**Book 4:** "Full Bloom" — mentor's secret revealed
[Each book gets full outline with clue placement map]

Best Practices

• Start with what excites you most. Whether it is a character, a world detail, or a single scene, lead with your strongest element. The skill builds the rest of the outline around your point of passion.

• Develop antagonists with equal depth. Request character profiles for your antagonist at the same detail level as your protagonist. Flat villains undermine even the strongest plot structure and theme.

• Test your outline against your theme. Every chapter should connect back to your central thematic question. If a chapter exists only for plot mechanics and does not touch the theme, it likely needs reworking.

• Use subplot count intentionally. Short stories need zero to one subplots. Novels need two to three. Series can sustain more. Over-plotting is the most common structural mistake in early outlines.

• Export and revise in your writing tool. The outline is a living document, not a rigid prescription. Export to Scrivener or Notion and modify as your draft teaches you what the story actually needs.

Common Issues

• Outline feels formulaic or paint-by-numbers. Switch the structure parameter from three-act to kishoetenketsu or a custom structure. Also increase detail_level so the skill generates more nuanced, story-specific beats rather than generic templates.

• Characters feel flat despite detailed profiles. Focus on contradictions and internal conflicts. Request the skill to identify where each character's stated values conflict with their actual behavior. That friction creates compelling characters.

• World-building overwhelms the plot. Set world_building: false for the first pass and outline pure character and plot. Add world details in a second pass, ensuring each world element serves the story rather than existing for its own sake.

Privacy & Data Handling

• Local Processing: All story development happens in your local Claude Code session. Your ideas, characters, and plot details are never transmitted to external servers or story databases.
• Data Retention: Outlines exist only in your current session and exported files. No creative work is stored, indexed, or used for any training purposes between sessions.
• Export Options: Export as Markdown, Scrivener OPML, Notion pages, or structured JSON. All files are written to your local filesystem with full ownership retained by you.
• Intellectual Property: All generated outlines, characters, and world-building elements are your creative property. The skill generates structural frameworks and suggestions that you own entirely.