skills/authors-build-place/SKILL.md
Build a place entry for the project bible via an interactive interview. Usage - /authors-build-place <name> [--author <author-name>]. Seven questions covering type, sensory signature, one odd detail, meaning to characters, how it changes, contradiction, connections. Optional --author lens (mcphee for architectural history, didion for cultural specificity). Use when you're adding a new location to a long-form project and want author personas to read its bible entry before editing passages set there.
npx skillsauth add sethshoultes/great-authors-plugin authors-build-placeInstall 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 structured place entry in the project bible.
Not for: writing scene prose set in this place (use /authors-channel <author> or /authors-draft); editing an existing passage (use /authors-edit).
Parse arguments: place name (required) + optional --author <name> flag. Valid lenses in v0.5: mcphee, didion. Others fall back to default.
Verify .great-authors/ exists. If not, tell the user to run /authors-project-init and stop.
Check for existing place file at .great-authors/places/<name>.md. If exists, ask about overwrite (default no).
Dispatch place-builder via Agent tool:
subagent_type: place-builderMode: interactive, Place name: <name>, Author lens: <author>, Working directory: <cwd>.Relay the interview. Seven questions, one at a time, user answers pass back verbatim.
Confirm creation:
Created .great-authors/places/<name>.md
Type: <type>
Sensory signature: <one-line summary>
Next: run /authors-channel <author> to draft a scene here, or /authors-build-place for the next location.
.great-authors/characters/ during the interview (question 7, connections), offer to run /authors-build-character next — after finishing this place file.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.