// Team composition for writing workflows: which agents to spawn, how many, what focus areas to assign, and how to scale effort. Use when composing critic panels, dispatching researchers, staffing draft/revise loops, or setting up brainstorm fan-outs.
Prose-level immersion patterns for narrative fiction. Use when writing or revising prose: the sentence-level and paragraph-level craft that pulls readers into the story. Project-specific voice comes from style files passed alongside this skill.
Adversarial reading methodology for narrative fiction: find what doesn't work, not confirm what does. Focus-area driven with dedicated resources per area. Use when reviewing drafts, evaluating prose quality, or assessing changes at any stage.
Arc structure, narrative design, and pacing at multiple scales: saga, arc, chapter, scene. Use when structuring story at any level, planning arcs, designing chapter outlines, or evaluating whether narrative structure serves the story's goals.
Story brainstorming capture: minimal notes that preserve creative freedom. Use when exploring narrative ideas, discussing characters, planning chapters, or thinking through story possibilities.
Logging and referencing writing issues: craft problems, tics, inconsistencies, and structural concerns found during analysis, critique, or review. Use when an agent identifies something worth tracking beyond a single critique report: repeated tics across chapters, inconsistencies that affect multiple scenes, structural problems that need the author's attention, or patterns that should be fixed in revision.
Load when producing any written artifact for humans.
| name | writing-staffing |
| type | reference |
| description | Team composition for writing workflows: which agents to spawn, how many, what focus areas to assign, and how to scale effort. Use when composing critic panels, dispatching researchers, staffing draft/revise loops, or setting up brainstorm fan-outs. |
| model-invocable | false |
Compose the right team for each writing task. The goal is coverage across perspectives: critics with different focus areas, researchers with different scopes, and brainstormers exploring different angles. Avoid redundant passes from the same angle.
Delegation keeps context clean. Each mode of work benefits from a fresh context window and different model strengths: drafting needs voice fidelity, critique needs adversarial distance, research needs breadth. Orchestrators coordinate mode-switches through agents. If no team composition was provided by your caller, compose one yourself before starting: use the catalogs in the resources below.
Review convergence. Critic loops run until convergence (no new substantive findings), not a fixed number of passes. The orchestrator can stop early, but must log the reasoning in the work directory so future agents understand what was decided and why.
Brainstorm diversity over brainstorm volume. Three brainstormers exploring different angles beats five exploring the same angle. Creative diversity comes from different perspectives, not more of the same perspective.
Style creation and style evaluation are separate modes. Creating style reference files from sample prose is an analytical task. Evaluating whether a draft maintains the project's voice is a critique task with voice focus. Use the right mode for each: see the agent catalogs in resources.
Effort scaling applies mainly to critics: the role that fans out within a draft/revise cycle. Writers don't scale within a phase (one writer per scene/chapter; split the brief if it's too big).
For critics, scale to the stakes and complexity of the content:
Think about what depends on what:
resources/knowledge.mdSee resources for detailed catalogs of available agents and when to use each:
resources/critique-synthesis.md when synthesizing findings from multiple critics: covers reward-channel triage.resources/critics.md when composing critique panels: covers critic focus areas and the continuity-checker specialist.resources/researchers.md when dispatching research: covers research focus areas and base agent usage.resources/builders.md when staffing writing, outlining, or style work: covers writer, outliner, style-creator, and base agents for wiki/reference pages.resources/knowledge.md when triggering knowledge maintenance: covers chronicler and base agent dispatch order.resources/character-sim.md when setting up character exploration: covers character-sim dispatch and multi-character fan-out patterns. Read it alongside resources/reader-sim.md when a workflow also needs experiential reader-response data on a draft.