nelson

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Nelson

Execute this workflow for the user's mission.

为用户的任务执行此工作流。

1. Issue Sailing Orders

1. 下达航行指令

Write one sentence for
```
outcome
```
,
```
metric
```
, and
```
deadline
```
.
Set constraints: token budget, reliability floor, compliance rules, and forbidden actions.
Define what is out of scope.
Define stop criteria and required handoff artifacts.

You MUST read

references/admiralty-templates.md

and use the sailing-orders template when the user does not provide structure.

为
```
outcome
```
、
```
metric
```
和
```
deadline
```
各撰写一句话。
设置约束条件：令牌预算、可靠性下限、合规规则以及禁止执行的操作。
定义超出范围的内容。
定义停止标准和所需的移交工件。

当用户未提供结构时，你必须阅读

references/admiralty-templates.md

并使用航行指令模板。

2. Form The Squadron

2. 组建中队

Brief captains on mission intent and constraints. Make the plan clear, invite questions early.
Select one mode:
```
single-session
```
: Use for sequential tasks, low complexity, or heavy same-file editing.
```
subagents
```
: Use for parallel scouting or isolated tasks that report only to admiral.
```
agent-team
```
: Use when independent agents must coordinate with each other directly.
Set team size from mission complexity:
Default to
```
1 admiral + 3-6 captains
```
.
Add
```
1 red-cell navigator
```
for medium/high threat work.
Do not exceed 10 squadron-level agents (admiral, captains, red-cell navigator). Crew are additional.
Assign each captain a ship name from
```
references/crew-roles.md
```
matching task weight (frigate for general, destroyer for high-risk, patrol vessel for small, flagship for critical-path, submarine for research).
Captain decides crew composition per ship using the crew-or-direct decision tree in
```
references/crew-roles.md
```
.

You MUST read

references/squadron-composition.md

for selection rules. You MUST read

references/crew-roles.md

for ship naming and crew composition. You MUST consult

references/standing-orders.md

before forming the squadron.

向舰长们简要介绍任务意图和约束条件。确保计划清晰，尽早邀请大家提问。
选择一种模式：
```
single-session
```
：适用于顺序任务、低复杂度工作或需频繁编辑同一文件的场景。
```
subagents
```
：适用于并行侦察或仅向舰队司令汇报的独立任务。
```
agent-team
```
：适用于独立Agent之间需要直接协调的场景。
根据任务复杂度设置团队规模：
默认配置为
```
1名舰队司令 + 3-6名舰长
```
。
对于中高风险任务，增加
```
1名红方导航员
```
。
中队级Agent（舰队司令、舰长、红方导航员）总数不得超过10名。船员为额外配置。
根据任务权重从
```
references/crew-roles.md
```
中为每位舰长分配舰船名称（护卫舰用于常规任务，驱逐舰用于高风险任务，巡逻艇用于小型任务，旗舰用于关键路径任务，潜艇用于研究任务）。
舰长需根据
```
references/crew-roles.md
```
中的“船员配置决策树”决定每艘船的船员组成。

你必须阅读

references/squadron-composition.md

以了解选择规则。你必须阅读

references/crew-roles.md

以了解舰船命名和船员组成规则。在组建中队前，你必须查阅

references/standing-orders.md

。

3. Draft Battle Plan

3. 制定作战计划

Split mission into independent tasks with clear deliverables.
Assign owner for each task and explicit dependencies.
Assign file ownership when implementation touches code.
Keep one task in progress per agent unless the mission explicitly requires multitasking.
For each captain's task, include a ship manifest. If crew are mustered, list crew roles with sub-tasks and sequence. If the captain implements directly (0 crew), note "Captain implements directly."

You MUST read

references/admiralty-templates.md

for the battle plan and ship manifest template. You MUST consult

references/standing-orders.md

when assigning files or if scope is unclear.

Before proceeding to Step 4: Verify sailing orders exist, squadron is formed, and every task has an owner, deliverable, and action station tier.

Crew Briefing: When spawning each teammate via

Task()

, you MUST include a crew briefing using the template from

references/admiralty-templates.md

. Teammates do NOT inherit the lead's conversation context — they start with a clean slate and need explicit mission context to operate independently.

将任务拆分为具有明确交付成果的独立子任务。
为每个子任务分配负责人和明确的依赖关系。
当涉及代码实现时，分配文件所有权。
除非任务明确要求多任务并行，否则每个Agent同一时间仅处理一个任务。
为每位舰长的任务准备舰船清单。若配置了船员，需列出船员角色及对应的子任务和执行顺序。若舰长直接执行任务（无船员），需标注“舰长直接执行”。

你必须阅读

references/admiralty-templates.md

以获取作战计划和舰船清单模板。在分配文件或范围不明确时，你必须查阅

references/standing-orders.md

。

进入步骤4前的检查： 确认已下达航行指令、中队已组建完成，且每个任务都有负责人、交付成果和行动岗层级。

船员简报： 当通过

Task()

生成每位队友时，你必须使用

references/admiralty-templates.md

中的模板提供船员简报。队友不会继承主导者的对话上下文——他们将从零开始，需要明确的任务上下文才能独立开展工作。

4. Run Quarterdeck Rhythm

4. 执行甲板节奏管控

Keep admiral focused on coordination and unblock actions.
The admiral sets the mood of the squadron. Acknowledge progress, recognise strong work, and maintain cheerfulness under pressure.
Run checkpoints at fixed cadence (for example every 15-30 minutes):
Update progress by task state:
```
pending
```
,
```
in_progress
```
,
```
completed
```
.
Identify blockers and choose a concrete next action.
Confirm each crew member has active sub-tasks; flag idle crew or role mismatches.
Track burn against token/time budget.
Re-scope early when a task drifts from mission metric.
When a mission encounters difficulties, you MUST consult
```
references/damage-control.md
```
for recovery and escalation procedures.

You MUST use

references/admiralty-templates.md

for the quarterdeck report template. You MUST consult

references/standing-orders.md

if admiral is doing implementation or tasks are drifting from scope. You MUST use

references/commendations.md

for recognition signals and graduated correction.

让舰队司令专注于协调工作和解决阻塞问题。
舰队司令需营造中队的工作氛围。认可进度，表扬出色工作，在压力下保持积极状态。
按固定节奏进行检查（例如每15-30分钟一次）：
根据任务状态（
```
pending
```
、
```
in_progress
```
、
```
completed
```
）更新进度。
识别阻塞问题并确定具体的下一步行动。
确认每位船员都有活跃的子任务；标记闲置船员或角色不匹配的情况。
跟踪令牌/时间预算的消耗情况。
当任务偏离任务指标时，尽早重新调整范围。
当任务遇到困难时，你必须查阅
```
references/damage-control.md
```
以获取恢复和升级流程。

你必须使用

references/admiralty-templates.md

中的甲板报告模板。若舰队司令参与具体实现或任务偏离范围，你必须查阅

references/standing-orders.md

。你必须使用

references/commendations.md

中的规则进行表扬和分级纠正。

5. Set Action Stations

5. 设置行动岗

You MUST read and apply station tiers from
```
references/action-stations.md
```
.
Require verification evidence before marking tasks complete:
Test or validation output.
Failure modes and rollback notes.
Red-cell review for medium+ station tiers.
Trigger quality checks on:
Task completion.
Agent idle with unverified outputs.
Before final synthesis.
For crewed tasks, verify crew outputs align with role boundaries (consult
```
references/crew-roles.md
```
and
```
references/standing-orders.md
```
if role violations are detected).

You MUST consult

references/standing-orders.md

if tasks lack a tier or red-cell is assigned implementation work.

你必须阅读并应用
```
references/action-stations.md
```
中的行动岗层级规则。
在标记任务完成前，要求提供验证证据：
测试或验证输出结果。
故障模式和回滚说明。
中高级行动岗需经过红方审查。
在以下场景触发质量检查：
任务完成时。
Agent处于闲置状态但输出未经验证时。
最终合成前。
对于配置船员的任务，验证船员输出是否符合角色边界（若发现角色违规，需查阅
```
references/crew-roles.md
```
和
```
references/standing-orders.md
```
）。

若任务未设置层级或红方人员被分配实现工作，你必须查阅

references/standing-orders.md

。

6. Stand Down And Log Action

6. 任务结束与日志记录

Stop or archive all agent sessions, including crew.
Produce captain's log:
Decisions and rationale.
Diffs or artifacts.
Validation evidence.
Open risks and follow-ups.
Mentioned in Despatches: name agents and contributions that were exemplary.
Record reusable patterns and failure modes for future missions.

You MUST use

references/admiralty-templates.md

for the captain's log template. You MUST use

references/commendations.md

for Mentioned in Despatches criteria.

停止或归档所有Agent会话，包括船员的会话。
生成船长日志：
决策及理由。
差异或工件。
验证证据。
未解决的风险和后续工作。
表彰名单：列出表现突出的Agent及其贡献。
记录可复用的模式和故障模式，以供未来任务参考。

你必须使用

references/admiralty-templates.md

中的船长日志模板。你必须使用

references/commendations.md

中的表彰名单评选标准。

Admiralty Doctrine

海军部准则

Optimize for mission throughput, not equal work distribution.
Prefer replacing stalled agents over waiting on undefined blockers.
Recognise strong performance; motivation compounds across missions.
Keep coordination messages targeted and concise.
Escalate uncertainty early with options and one recommendation.

以任务吞吐量为优化目标，而非平均分配工作。
优先替换停滞的Agent，而非等待未明确的阻塞问题解决。
认可出色表现；积极性会在多次任务中持续积累。
协调信息需针对性强且简洁。
尽早上报不确定性，并提供可选方案和一项推荐建议。