skills/authors-build-relationship/SKILL.md
Build a relationship entry between two existing characters in the project bible. Usage - /authors-build-relationship <character-a> <character-b>. Six questions covering type, power dynamic, history, current conflict, shared vocabulary, secrets and wrong assumptions. Updates the
npx skillsauth add sethshoultes/great-authors-plugin authors-build-relationshipInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Build a relationship entry between two existing characters.
Not for: creating new characters (use /authors-build-character); drafting a scene between them (use /authors-channel <author> or /authors-draft).
Parse arguments: both character names required. Lowercase, hyphenated (matching the character file names).
Verify both character files exist:
.great-authors/characters/<character-a>.md.great-authors/characters/<character-b>.mdIf either is missing, tell the user and offer to run /authors-build-character for the missing one first. Do not proceed until both exist.
Verify characters are different. If <character-a> and <character-b> are the same, ask the user to pick a different second character.
Check for existing connection between them in either file's ## Connections section. If found, ask: extend / replace / cancel. Default extend.
Dispatch relationship-builder via Agent tool:
subagent_type: relationship-builderMode: interactive, Character A: <name>, Character B: <name>, Working directory: <cwd>.Relay the interview. Six questions, one at a time.
Confirm update:
Updated .great-authors/characters/<character-a>.md and .great-authors/characters/<character-b>.md
Type: <type>
Live tension: <one-line>
Next: run /authors-channel <author> to draft a scene between them, or /authors-build-relationship for another pair.
documentation
Dispatch a named author persona as a sub-agent to rewrite an existing manuscript file from scratch with full bible context. Usage - /authors-rewrite <file> <author>. Use when an existing chapter or scene needs more than a critique pass — when the prose itself isn't working and a clean rewrite by the named author is required. The skill assembles a self-contained brief (bible files, prior/next chapters, architecture beats, voice rules), dispatches the author, and confirms save.
tools
Top-level autonomous workflow for writing a novel end-to-end with the great-authors plugin. Composes existing skills (project-init, build-character, build-place, build-relationship, draft, channel, rewrite, continuity, critique, edit, debate, journal, consolidate) into a multi-phase pipeline with human checkpoints. The human provides direction (premise, genre, characters, voice); the AI orchestrator dispatches author personas as sub-agents to do the work. Use when a user wants the full great-authors pipeline run for them with minimal hand-holding — analogous to great-minds-plugin's agency-* workflows. Usage - /authors-orchestrate-novel, optionally with --phase <N> to run a single phase or --resume to continue from the last checkpoint.
data-ai
Run ONE editor across MULTIPLE files in parallel, then consolidate into a corpus-level pattern report. Surfaces patterns no per-file critique catches — voice drift, recurring tics, structural failures that only become visible across multiple pieces. Usage - /authors-corpus-critique <author> <path-or-glob> [<path-or-glob>...]. Different from /authors-critique (N authors on 1 file). This is 1 author on N files.
tools
Initialize the per-project memory bible (.great-authors/) in the current working directory. Creates project.md, voice.md, timeline.md, glossary.md, and empty characters/, places/, scenes/ directories. Use when the user is starting a new writing project (novel, essay collection, long-form nonfiction) and wants author personas to have persistent context across sessions.