narrative-architect

To turn world-building documents into narrative blueprints, analyze foundation docs like world-bible and design-pillars to generate structured story-arcs, character-profiles, key-scenes, and quest-hooks. This reduces ambiguity by converting high-level lore into concrete specifications writers can implement.

Expanding a narrative bible into story-arcs and character-profiles involves reading foundation design documents and synthesizing their world-building elements into detailed beats, trajectories, and quest-hooks. The process outputs four structured markdown documents that downstream dialogue teams use for implementation.

Yes, generating narrative design-docs requires foundation documents. The skill reads from docs/design/world-bible.md, docs/design/narrative-bible.md, and docs/design/design-pillars.md to maintain consistency across the game's narrative and ensure accurate story expansion.

Yes, you can use this narrative world-building approach for existing game design pillars. The skill integrates design-pillars.md alongside world-bible and narrative-bible documents to ensure generated story-arcs and quest-hooks remain consistent with your established game design.

The generated narrative documentation gets saved directly into your project's docs/narrative/ directory. The skill outputs four markdown files: story-arcs.md, character-profiles.md, key-scenes.md, and quest-hooks.md for downstream designers to access immediately.

The best way to structure quest-hooks from a world-bible is to analyze the foundation document's world-building elements and expand them into actionable narrative specifications. This produces dedicated quest-hooks documentation that aligns with your character-profiles and story-arcs.