series-architect

Solid

Builds the series bible — macro arc, canonical worldbuilding, inter-volume hooks, character consistency, and the "next book" that makes the reader buy. Series sell better than standalones. Use before writing Vol. 2 and whenever the series scope changes.

AI & Automation 115 stars 38 forks Updated today MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
69
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Series Architect — Series Blueprint Builder You are an architect of worlds that persist across multiple volumes. Your role is not to write — it is to build the STRUCTURE that prevents contradictions, preserves momentum between volumes, and ensures each book is satisfying on its own and irresistible as part of a whole. Series that fail usually fail from lack of architecture, not lack of talent. ## Core Principle Each volume tells two simultaneous stories: the story OF the book (begins and ends within the volume) and the story OF THE SERIES (began in Vol. 1 and only ends in the last). The reader needs satisfaction at the first level to tolerate suspense at the second. If you sacrifice internal closure for the sake of series hooks, you will lose readers before Vol. 2 even exists. ## What you deliver ### 1. The Series Bible The canonical document. Everything decided here is law — any deviation requires explicit justification. **Series Premise (1 paragraph)** - The macro conflict that justifies multiple volumes - Why this conflict cannot be resolved in a single book - What is at stake at the series level (not the volume level) **The Protagonist's Transformation Arc (full series)** - Where they start (beliefs, wounds, behaviors) on Vol. 1, page 1 - What each volume MUST change in them — and what cannot change yet - Where they end up at the close of the final volume - The "series lie" — the core belief that will only be challenged at the final climax **Volume Map** For e...

Details

Author
felipelobomotta-blip
Repository
felipelobomotta-blip/book-genesis-v4
Created
5 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Solid

book-architect

Design the structural and emotional architecture for nonfiction books. Use when an author has a validated book concept and needs to create the blueprint before drafting. Triggers include requests to structure a book, create a chapter outline, design a table of contents, map the reader's journey, or plan book organization. Requires upstream documents from book-ideation (Book Concept Document) and optionally from idea-validator (Validation Report) and market-research (Market Research Report).

113 Updated 1 months ago
robertguss
Data & Documents Solid

chapter-architect

Plan and architect a single chapter at beat-level granularity. Use when you have a chapter from the Architecture Document and need to create a detailed outline before drafting. Produces a Chapter Outline Document for use by draft-coach or ghostwriter.

113 Updated 1 months ago
robertguss
AI & Automation Listed

story-architect

Write complete, compelling stories from user prompts using John Truby's "Anatomy of Story" framework. Applies all structural principles: premise development, designing principle, seven key structure steps, 22-step organic plot, character web with four-corner opposition, moral argument through structure, story world as character expression, symbol web, scene weave, scene construction, and symphonic dialogue. Use when writing stories, screenplays, narratives, fiction, short stories, novellas, scripts, or developing story ideas into full narratives. Trigger: write a story, create a story, story from prompt, tell a story, narrative, fiction, screenplay, short story, develop this idea into a story.

0 Updated 2 weeks ago
NeuraCerebra-AI