skills/authors-debate/SKILL.md
Run a 2-round craft debate between two named author personas on a specific passage or topic. Usage - /authors-debate <passage-or-topic> <author-A> <author-B>. Round 1 - each states their position. Round 2 - each responds to the other. Consolidation names the real tension and picks a winner or offers a third option. Use when you genuinely don't know how to handle a craft choice (e.g., Hemingway vs. McCarthy on whether a scene needs muscle or weight).
npx skillsauth add sethshoultes/great-authors-plugin authors-debateInstall 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.
Two-round craft dispute resolution.
Not for: general critique (/authors-critique); marked-up editing (/authors-edit); collaborative drafting (/authors-channel).
Parse arguments:
<passage-or-topic> (required). Can be a quoted passage (string) or a file path (if the token resolves to an existing file, load it).<author-A> and <author-B> (both required). Valid author names from the roster. Must be two different authors.If passage is a file path, read the file. If it's inline text, use as-is.
Round 1 — parallel. Dispatch both authors in parallel (single message, two Agent calls):
subagent_type: <author-A>-persona / <author-B>-personaDEBATE ROUND 1.
The topic: <passage or topic, full text>
State your position in 3-5 sentences. What would you do with this? Why? What would be wrong with treating it another way? Be specific about your craft reasoning. Do not hedge.
Do NOT respond to other voices yet — you don't know what they'll say. Just state your own position.
Round 2 — parallel. Once both Round 1 responses are in, dispatch again in parallel:
DEBATE ROUND 2.
In Round 1 you said:
<author's Round 1 response>
<opposing author> said:
<opposing author's Round 1 response>
Respond in 3-5 sentences:
- What do you concede? (If nothing, say so and explain.)
- Where do you hold your position?
- If you'd revise your Round 1 position, how?
Consolidate. Write the debate report:
# /authors-debate: <author-A> vs. <author-B>
**Topic:** <passage or topic as given>
## Round 1
### <Author A>
<their R1 position>
### <Author B>
<their R1 position>
## Round 2
### <Author A>
<their R2 response>
### <Author B>
<their R2 response>
## The real tension
(One or two sentences naming what this dispute is actually about — usually a genre, register, or audience question. E.g., "The tension is whether this scene's weight comes from compression (A) or accumulation (B). That's a register choice determined by the genre.")
## Verdict
Pick ONE:
- **Winner:** <author name> — <one sentence reason>
- **Third way:** <a synthesis neither author proposed, if one exists>
- **Consensus:** <synthesized brief — when both authors converge, with refinements from Round 2 incorporated. Use when authors agreed in Round 1 and Round 2 produced a sharper joint position than either had alone. The consensus brief should be specific enough that an orchestrator can pass it directly to a rewrite without re-synthesizing.>
- **Genre call:** <the choice depends on <X>; here's how to decide>
Output to stdout. No manuscript changes.
.great-authors/voice.md establishes a house style for the project, both debaters should respect it in their reasoning (but they can argue for what the voice SHOULD be if the user is questioning it)./authors-rewrite) without further synthesis. Use it when applicable; do not force a fake disagreement to satisfy the Winner / Third way framing.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.