writing-staffing

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Writing Staffing

写作人员配置

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.

为每项写作任务组建合适的团队。目标是覆盖不同视角：拥有不同专注领域的评审员、不同研究范围的研究人员，以及探索不同角度的头脑风暴参与者。避免从同一角度进行重复工作。

General Principles

通用原则

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 decision log 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.

委派任务保持上下文清晰。 每种工作模式都受益于全新的上下文窗口和不同的模型优势：起草需要语音保真度，评审需要对抗性距离，研究需要广度。编排器通过Agent协调模式切换。如果调用方未提供团队组成，在开始前自行组建：使用下方资源中的目录。

评审收敛。 评审循环持续到收敛（无新的实质性发现），而非固定次数的迭代。编排器可以提前终止，但必须在决策日志中记录推理过程，以便后续Agent了解决策内容及原因。

头脑风暴重多样性而非数量。 三名探索不同角度的头脑风暴参与者胜过五名探索同一角度的参与者。创意多样性来自不同视角，而非同一视角的重复叠加。

风格创建与风格评估是独立模式。 从示例散文创建风格参考文件是一项分析任务。评估草稿是否保持项目的语音风格是一项专注于语音的评审任务。为每项任务使用正确的模式：请参阅资源中的Agent目录。

Effort Scaling

工作力度调整

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:

Low-stakes drafts (brainstorm captures, wiki stubs): 1-2 critics
Standard chapters: 3 critics with split focus areas
Pivotal scenes (character deaths, reveals, arc climaxes): 4-5 critics; for critical focus areas like voice consistency and continuity, duplicate coverage

工作力度调整主要适用于评审员：即在草稿/修订循环中进行发散工作的角色。作家不会在一个阶段内增加人数（每个场景/章节一名作家；如果任务过大则拆分简报）。

对于评审员，根据内容的重要性和复杂度调整规模：

低重要性草稿（头脑风暴记录、维基条目草稿）：1-2名评审员
标准章节：3名专注领域拆分的评审员
关键场景（角色死亡、揭秘、剧情高潮）：4-5名评审员；对于语音一致性和连贯性等关键专注领域，安排重复覆盖

Parallelism

并行性

Think about what depends on what:

Critics need a finished draft: they wait for the writer
Critics examine different dimensions: fan them all out simultaneously
Within a brainstorm fan-out, all brainstormers are independent: fan them out
Knowledge maintenance has ordering constraints: see
```
resources/knowledge.md
```
Character simulations in a multi-character scene are independent: fan them out, then synthesize

思考任务之间的依赖关系：

评审员需要完整的草稿：他们需等待作家完成
评审员检查不同维度：将他们全部并行部署
在头脑风暴发散架构中，所有头脑风暴参与者都是独立的：并行部署他们
知识维护有顺序约束：请参阅
```
resources/knowledge.md
```
多角色场景中的角色模拟是独立的：并行部署，然后进行综合

Agent Catalogs

Agent目录

See resources for detailed catalogs of available agents and when to use each:

Read
```
resources/critique-synthesis.md
```
when synthesizing findings from multiple critics: covers reward-channel triage.
Read
```
resources/critics.md
```
when composing critique panels: covers critic focus areas and the continuity-checker specialist.
Read
```
resources/researchers.md
```
when dispatching research: covers research focus areas and base agent usage.
Read
```
resources/builders.md
```
when staffing writing, outlining, or style work: covers writer, outliner, style-creator, and base agents for wiki/reference pages.
Read
```
resources/knowledge.md
```
when triggering knowledge maintenance: covers chronicler and base agent dispatch order.
Read
```
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.

请参阅资源获取可用Agent的详细目录及使用场景：

综合多名评审员的发现时，请阅读
```
resources/critique-synthesis.md
```
：涵盖奖励渠道分类。
组建评审小组时，请阅读
```
resources/critics.md
```
：涵盖评审员专注领域和连贯性检查专家。
分派研究任务时，请阅读
```
resources/researchers.md
```
：涵盖研究专注领域和基础Agent使用方法。
安排写作、大纲或风格工作时，请阅读
```
resources/builders.md
```
：涵盖作家、大纲撰写者、风格创建者，以及维基/参考页面的基础Agent。
触发知识维护时，请阅读
```
resources/knowledge.md
```
：涵盖记录员和基础Agent的分派顺序。
搭建角色探索架构时，请阅读
```
resources/character-sim.md
```
：涵盖角色模拟Agent的分派和多角色发散模式。当工作流还需要草稿的体验式读者反馈数据时，请同时阅读
```
resources/reader-sim.md
```
。