worldsmith

Apply a change to the worldbuilding project — edits, new ideas, or promotions

Run read-only diagnostics on the worldbuilding project. Do NOT modify any files. Report findings and let the user decide what to act on.

Show worldsmith commands, skills, and typical workflows

Scaffold or adopt a worldbuilding documentation ecosystem

Launch multi-agent editorial review — consistency, craft, voice, and structure auditors in parallel

Specialist agent for character voice, arcs, and relationships. Launched by the writer orchestrator during multi-agent content generation. Develops character documentation with behavioral specificity — voice patterns testable against dialogue, emotional flickers anchored to moments, and relationship maps with bidirectional behavioral signatures. <example> Context: Orchestrator needs voice patterns developed for a protagonist. user: "Develop Maren's voice patterns and speech tics so the scene-writer can write her dialogue" assistant: "I'll launch the character-developer to build Maren's voice spec — rhetorical habits, stress markers, metaphor families, and patterns specific enough that the voice-auditor can verify dialogue against them." </example> <example> Context: Orchestrator needs a character arc mapped with emotional flickers. user: "Map Kael's arc from chapter 3 through chapter 12 with specific emotional beats" assistant: "I'll launch the character-developer to trace Kael's trajectory — anchored emotional flickers at each chapter, the setbacks that make the arc feel earned, and notes for the scene-writer on how his voice shifts as the arc progresses." </example>

Specialist agent for objective consistency verification in fiction manuscripts. Launched by the reviewer orchestrator during multi-agent review. Checks timeline, factual, character state, and spatial consistency against canonical documentation. Does not evaluate prose quality, voice, or structure. <example> Context: Orchestrator needs timeline and factual consistency verification. user: "Check this manuscript against the canonical docs for contradictions" assistant: "I'll launch the consistency-auditor to verify timeline, facts, character state, and spatial consistency." </example> <example> Context: Orchestrator needs to verify manuscript after canonical doc changes. user: "The timeline was updated — check the manuscript for new contradictions" assistant: "I'll launch the consistency-auditor to compare the manuscript against the updated canonical docs." </example>

Specialist agent for prose craft analysis in fiction manuscripts. Launched by the reviewer orchestrator during multi-agent review. Finds show-don't-tell violations, dialogue craft failures, sentence-level weaknesses, and scene mechanic problems. Runs mechanical pattern counts via count_patterns.py and layers analytical judgment on top. Does not evaluate consistency, voice, or structure — only prose quality. <example> Context: Orchestrator needs prose craft analysis during multi-agent review. user: "Audit the manuscript for prose craft issues — cliches, telling, weak dialogue" assistant: "I'll launch the craft-auditor to analyze prose quality: show-don't-tell, dialogue craft, sentence mechanics, and scene structure." </example> <example> Context: Orchestrator needs pattern counts and craft analysis after a major revision pass. user: "Run a full prose audit including pattern counts on the revised chapters" assistant: "I'll launch the craft-auditor to run count_patterns.py and perform analytical prose review on the revised manuscript." </example>

Specialist agent for worldbuilding content generation — history, mythology, cultures, and systems. Launched by the writer orchestrator during multi-agent content generation. Develops canonical documentation with narrative prose quality and consequence chains. <example> Context: Orchestrator needs world history developed for a kingdom. user: "Develop the history of the Northern Kingdom from founding through the civil war" assistant: "I'll launch the lore-writer to build the Northern Kingdom's history — geological constraints, founding myths, political evolution, and the civil war's causes and aftermath." </example> <example> Context: Orchestrator needs a magic system designed with full consequences. user: "Design a resonance-based magic system and derive its societal implications" assistant: "I'll launch the lore-writer to design the resonance magic system — mechanics, costs, power structures, economic implications, and cultural attitudes." </example>

Multi-agent fiction review orchestrator. Acts as editorial director: reads the project, spawns specialist reviewers (parallel), cross-verifies critical findings, and synthesizes a unified editorial report to .worldsmith/reviews/. <example> Context: User wants a thorough autonomous review of their fiction manuscript. user: "Do a thorough review of my manuscript" assistant: "I'll launch the reviewer agent for a comprehensive multi-agent editorial review." </example> <example> Context: User wants specific chapters reviewed. user: "Critique chapters 3-5" assistant: "I'll launch the reviewer agent to run all four specialists against chapters 3 through 5." </example> <example> Context: User wants a full consistency and craft pass before publishing. user: "Review my novel for consistency and craft issues" assistant: "I'll launch the reviewer agent for a full editorial review — consistency, craft, voice, and structure." </example> <example> Context: User wants a comprehensive editorial report. user: "Full editorial review" assistant: "I'll launch the reviewer agent to orchestrate all four specialist auditors and produce a unified report." </example>

Use when writing fiction, editing fiction prose, reviewing chapters, or drafting scenes. Covers prose craft, dialogue mechanics, scene structure, and common failure modes in AI-assisted fiction. Trigger phrases: "write fiction", "edit chapter", "prose review", "scene draft", "dialogue check", "fiction craft", "edit this scene", "review my prose".

This skill should be used when the user asks about "documentation structure", "doc relationships", "cross-references", "propagation", "canonical workflow", "exploratory workflow", "docs-first", "lore management", "worldbuilding docs", "consistency rules", "canonical hierarchy", "update docs", "change propagation", "editorial workflow", "Silmarillion approach", or is working in a project with a worldbuilding documentation ecosystem (docs/ or lore/ directory).

4 hooks across 3 events