ailabs-393/ai-labs-claude-storyboard-manager
Assist writers with story planning, character development, plot structuring, chapter writing, timeline tracking, and consistency checking. Use this skill when working with creative writing projects organized in folders containing characters, chapters, story planning documents, and summaries. Trigger this skill for tasks like "Help me develop this character," "Write the next chapter," "Check consistency across my story," or "Track the timeline of events.
This is a copy. The original lives at ailabs-393/storyboard-manager.
npx skills add https://github.com/ailabs-393/ai-labs-claude-skills --skill storyboard-manager
The Storyboard Manager skill equips Claude with specialized knowledge and tools for creative writing workflows. It provides frameworks for character development, story structure patterns, automated timeline tracking, and consistency checking across narrative projects. This skill automatically adapts to various storyboard folder structures while maintaining best practices for novel, screenplay, and serialized fiction writing.
The skill provides four main capabilities:
Support creating deep, consistent character profiles with backstories, arcs, and relationships.
Guide plot development using established frameworks (Three-Act, Hero's Journey, Save the Cat, etc.) and help organize narrative elements.
Generate chapter content, scene breakdowns, and dialogue that maintains consistency with established characters and plot.
Use automated tools to verify chronological consistency, character continuity, and world-building coherence.
The Storyboard Manager automatically detects and adapts to various folder organizations. Look for these common directory patterns:
Character folders: characters/, Characters/, cast/, Cast/
Chapter folders: chapters/, Chapters/, scenes/, Scenes/, story/
Planning folders: story-planning/, planning/, outline/, notes/
Summary files: summary.md, README.md, overview.md
When triggered, scan the project root to identify the structure and adjust workflows accordingly. If no standard structure exists, recommend organizing files using the pattern: characters/, chapters/, story-planning/, and summary.md.
Use this decision tree to determine the appropriate workflow:
User Request
├─ Character-related? ("develop character," "create backstory," "character arc")
│ └─ → Character Development Workflow
│
├─ Planning/Plot? ("outline story," "plan act 2," "plot structure")
│ └─ → Story Planning Workflow
│
├─ Writing content? ("write chapter," "generate scene," "continue story")
│ └─ → Chapter/Scene Writing Workflow
│
└─ Checking/Analysis? ("check consistency," "track timeline," "find contradictions")
├─ Timeline? → Use timeline_tracker.py script
└─ Consistency? → Use consistency_checker.py script
Before developing a character, read existing character files to understand:
Use the Read tool to examine existing character files in the characters directory.
When detailed character guidance is needed, read references/character_development.md which contains:
To efficiently find specific guidance, use Grep to search for relevant sections:
# Example: Find guidance on character arcs
grep -i "character arc" references/character_development.md
Create or enhance character profiles with these essential elements:
Basic Information
Background
Character Arc
Relationships
Unique Elements
Cross-reference with:
Write the character profile to characters/[character-name].md using markdown format. Match the existing style and structure found in other character files.
Read existing planning documents to understand:
Look in folders like story-planning/, outline/, or files like summary.md.
For detailed structural guidance, read references/story_structures.md which includes:
Use Grep to find specific frameworks:
# Example: Find Three-Act Structure details
grep -A 20 "Three-Act Structure" references/story_structures.md
Based on the user's request and story genre, recommend appropriate frameworks:
Create or enhance planning documents with:
Story Overview
Plot Structure
Character Arcs
World-Building Elements (if applicable)
Timeline
Write planning documents to story-planning/[document-name].md. Use clear hierarchical structure with markdown headers for easy navigation.
Before writing any content, comprehensively read:
Character Files: All relevant character profiles to understand voices, motivations, arcs
Planning Documents: Story structure, plot points, current story position
Previous Chapters: Recent chapters to maintain continuity (read at least 1-2 prior chapters)
Summary: Overall story premise and themes
This ensures the new content aligns with established elements.
Determine:
Apply scene structure components:
Scene (Action)
Sequel (Reaction)
Alternate between high-tension (action, conflict) and low-tension (reflection, world-building) beats for pacing.
Maintain character voice by referencing:
Include timeline references to maintain chronological clarity:
Timeline: Day 5, Evening in chapter header or as section breakWrite chapter content to chapters/chapter-[number].md or chapters/[chapter-name].md. Include:
Chapter Header
# Chapter [Number]: [Optional Title]
**Timeline:** [When this occurs]
**POV:** [Character name]
**Location:** [Where this takes place]
Chapter Content
After writing, document any new information introduced:
This helps maintain consistency in future chapters.
Invoke the timeline tracker when:
Execute the script from the project root:
python3 .claude/skills/storyboard-manager/scripts/timeline_tracker.py . --output markdown
Output format options:
markdown - Human-readable report (default)json - Structured data for further processingThe script provides:
Statistics
Timeline View
Warnings
After running the tracker:
Add timeline markers to chapters where missing:
**Timeline:** Day 7, Morning
Or use inline markers:
Three days had passed since the incident...
Invoke the consistency checker when:
Execute the script from the project root:
python3 .claude/skills/storyboard-manager/scripts/consistency_checker.py . --output markdown
Output format options:
markdown - Human-readable report with issue details (default)json - Structured data for programmatic analysisThe script identifies issues in three severity levels:
Critical (🔴)
Warning (⚠️)
Info (ℹ️)
For each issue reported:
Example workflow for character age inconsistency:
Issue: Age inconsistency for Maya
- Profile: 18 years old
- Chapter 3: mentions "21-year-old Maya"
Fix: Edit chapter-3.md to change "21-year-old" to "18-year-old"
The automated checker catches:
The checker cannot catch:
Manual review is still essential for deep consistency.
Don't load all reference files at once. Instead:
Match the story's established tone:
Reference the summary.md to identify target audience and adjust accordingly.
Every chapter should serve character arcs:
For narrative writing:
When stories have multiple perspectives:
Python script that analyzes markdown files to extract and organize timeline events. Tracks character appearances, identifies time markers, groups events chronologically, and flags consistency issues.
Usage: Run from project root with python3 .claude/skills/storyboard-manager/scripts/timeline_tracker.py .
Python script that detects inconsistencies in character details, physical descriptions, ages, names, and world-building facts across all story files. Outputs severity-ranked issues with file locations.
Usage: Run from project root with python3 .claude/skills/storyboard-manager/scripts/consistency_checker.py .
Comprehensive framework for creating multi-dimensional characters including core elements, backstory structure, arc types, relationship dynamics, voice development, and consistency guidelines.
Load when: Developing new characters, enhancing existing profiles, resolving character consistency issues, or planning character arcs.
Detailed reference covering major story structures (Three-Act, Hero's Journey, Save the Cat), character arc templates, scene structure, pacing guidelines, plot development techniques, and genre-specific structures.
Load when: Planning story outline, structuring acts, organizing plot beats, determining pacing, or applying specific narrative frameworks.
Take ailabs-393/ai-labs-claude-storyboard-manager from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.