series-architect

Create a canonical Series Bible with world rules, character arcs, and volume maps.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/PhilipStark/book-genesis --skill series-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: series-architect
Source: https://github.com/PhilipStark/book-genesis/tree/main/skills/series-architect
Command: npx skills add https://github.com/PhilipStark/book-genesis --skill series-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Series Architect builds the canonical Series Bible to prevent contradictions across volumes and ensure cohesive worldbuilding and timeline consistency across the entire series.

Core Features & Use Cases

  • Series Bible with canonical documents
  • Canonical worldbuilding, timeline, and character management across volumes
  • Inter-volume hooks and consistency checks to maintain momentum
  • Quick-start prompts and templates to bootstrap planning across volumes

Quick Start

Provide the Vol. 1 premise, planned volume count, and core protagonist to generate the Series Bible.

Frequently Asked Questions about series-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a series bible for cross-volume continuity?

Generate a series bible by inputting your Vol. 1 premise, planned volume count, and core protagonist to produce a formatted document tracking world rules, character arcs, and inter-volume hooks.

What is a series bible used for in multi-volume story architecture?

A series bible prevents contradictions across volumes by unifying canonical worldbuilding, timeline management, and character arcs, while anchoring inter-volume hooks to maintain narrative momentum throughout the series.

How do I track character arcs and world rules across multiple volumes?

Track character arcs and world rules across volumes by mapping them into a structured schema containing a protagonist's transformation arc, canonical world rules, a volume map, and a glossary.

Can I plan inter-volume hooks for a series without existing story outlines?

Planning inter-volume hooks requires a Vol. 1 premise, planned volume count, and core protagonist to bootstrap the series architecture and generate a formatted series bible document.

Does this series architecture approach work for tracking timeline consistency across an entire series?

Yes, the series architecture approach handles timeline consistency by applying canonical worldbuilding and timeline management across volumes, enforcing strict continuity checks within the generated series bible.

What is the best way to prevent worldbuilding contradictions across a planned book series?

The best way to prevent worldbuilding contradictions is to create a canonical series bible that enforces cross-volume continuity through structured consistency checks and unified world rules.