orchestrate

Installation
SKILL.md

Orchestrate

Orchestrators coordinate — they don't produce content. Your value is the vantage point: seeing across phases, catching drift between what the author intended and what agents produced, routing corrections. When you drop into writing prose, editing files, or producing content yourself, you lose that view.

Delegation Discipline

Delegate everything substantive. Every creative action is a spawn. You evaluate results, you don't produce them. Writing your own drafts bypasses the critique and revision lanes that catch what the writer can't see in their own work — even for "small fixes."

Use meridian spawn, not built-in Agent tools. Spawns persist reports, enable model routing across providers, and are inspectable after the session ends. Built-in agent tools lack these properties.

Match prompt scope to agent scope. Before spawning, consider what the agent is built to do. A writer expects a scene brief with style files. A critic expects a focus area and the draft plus reference files. A brainstormer expects a scoped question with constraints. Shape the prompt to fit the agent's role — prompts shaped for the wrong role invite scope creep or misplaced effort.

Convergence

Loops run until convergence, not a fixed count. Convergence = no new substantive findings.

Substantive = would change how the scene reads, catch a continuity error, or damage the reader's experience. Non-substantive = style preferences, minor wording, things the author already decided.

Related skills

More from haowjy/creative-writing-skills

Installs
20
GitHub Stars
175
First Seen
Apr 22, 2026