npx skills add https://github.com/harrymunro/nelson --skill nelson为用户的任务执行此工作流程。
outcome、metric 和 deadline 各写一句话。当用户未提供结构时,您必须阅读 references/admiralty-templates/sailing-orders.md 并使用航行指令模板。
航行指令摘要示例:
Outcome: Refactor auth module to use JWT tokens
Metric: All 47 auth tests pass, no new dependencies
Deadline: This session
Constraints: Do not modify the public API surface
Out of scope: Migration script for existing sessions
会话卫生: 在组建中队之前,根据 references/damage-control/session-hygiene.md 执行会话卫生。清除任何先前会话中的陈旧损坏报告和交接简报。恢复中断的会话时跳过此步骤。
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
single-session:用于顺序任务、低复杂度或大量同文件编辑。subagents:用于并行侦察或仅向海军上将报告的独立任务。agent-team:用于需要独立智能体之间直接协调的情况。1 名海军上将 + 3-6 名舰长。1 名红队领航员。references/crew-roles.md 中为每位舰长分配一个匹配的舰船名称。references/crew-roles.md 中的船员或直接执行决策树来决定每艘船的船员构成。references/royal-marines.md 并使用 references/admiralty-templates/marine-deployment-brief.md 作为部署简报。references/model-selection.md。对所有 Agent 工具调用应用基于权重的模型选择,并为分配给俳句模型的智能体包含俳句简报增强功能。选择规则参考 references/squadron-composition.md,舰船命名和船员构成参考 references/crew-roles.md。在组建中队之前,请查阅下面的常备指令表。
作战计划模板参考 references/admiralty-templates/battle-plan.md,舰船清单参考 references/admiralty-templates/ship-manifest.md。在分配文件或范围不明确时,请查阅下面的常备指令表。
在进入第 4 步之前: 确认航行指令存在,中队已组建,并且每个子任务都有负责人、交付成果和行动站等级。
海军上将行动清单: 对于每个子任务,有意识地标记 admiralty-action-required: 为 yes 或 no。然后扫描作战计划中标记为 admiralty-action-required: yes 的子任务。如果存在任何此类子任务,在生成任何智能体之前,向用户呈现一份海军上将行动清单:
ADMIRALTY ACTION LIST — Actions required from Admiralty
1. [Task name]
action: [what you must do]
timing: [before task starts | after task completes]
unblocks: [task name or stand-down]
No action needed now. These will be raised by the captain when each step is reached.
如果没有子任务标记为 admiralty-action-required: yes,则省略该清单——常规任务无需噪音。此清单是信息性的,不是关卡。用户通过继续对话来确认。中队组建在此之后立即进行。
船员简报: 生成和任务分配是两个步骤。首先,使用 Agent 工具生成每位舰长,并在其提示中包含来自 references/admiralty-templates/crew-briefing.md 的船员简报。然后使用 TaskCreate + TaskUpdate 创建并分配工作。队友不会继承领队的对话上下文——他们从零开始,需要明确的任务上下文。各模式完整参数详情参见 references/tool-mapping.md。
交接简报: 当一艘船因上下文耗尽而被替换时,它应使用 references/admiralty-templates/turnover-brief.md 撰写一份交接简报。完整程序参见 references/damage-control/relief-on-station.md。
TaskList 中的任务状态(pending、in_progress、completed)来更新进度。SendMessage 为舰长解锁或调整其方法。references/standing-orders/paid-off.md。仅当中航行指令中指定的重新分配任务的触发条件尚未评估时,才保留一艘船。references/damage-control/hull-integrity.md 采取行动。海军上将在每次检查点也必须检查自身的船体完整性。references/admiralty-templates/quarterdeck-report.md。即使船体状态为绿色,也不要跳过此步骤——压缩可能随时发生,磁盘上的报告是唯一的恢复点。TaskList 中是否有描述以 [AWAITING-ADMIRALTY]: 为前缀的子任务。如果存在,立即向海军上将提出请求——不要等到下一个检查点。TaskList 进行交叉比对:对于作战计划中标记为 admiralty-action-required: yes 且状态显示为 completed 的任何子任务,确认存在记录海军上将签字的季度甲板日志条目。如果不存在这样的条目,则向海军上将标记以进行手动验证——该子任务可能在未完成预期的人工步骤的情况下就完成了。后甲板检查点示例:
Status: 3/5 tasks complete, 1 blocked, 1 in progress
Blocker: HMS Resolute waiting on API schema from HMS Swift
Action: Redirect HMS Swift to prioritise schema export
Budget: ~40% tokens consumed, on track
Hull: All ships green
协调工具参考 references/tool-mapping.md,报告模板参考 references/admiralty-templates/quarterdeck-report.md,损坏报告格式参考 references/admiralty-templates/damage-report.md。使用 references/commendations.md 进行认可信号和渐进式纠正。如果海军上将正在执行实施工作或子任务偏离范围,请查阅下面的常备指令表。
references/action-stations.md 中的站级规定。references/crew-roles.md 和下面的常备指令表)。references/royal-marines.md 中的行动站等级规则。2 级及以上的陆战队部署需要海军上将批准。红队审查模板参考 references/admiralty-templates/red-cell-review.md。如果子任务缺少等级或红队被分配了实施工作,请查阅下面的常备指令表。
captains-log.md 的文件。日志必须写入磁盘——仅输出到聊天窗口不满足此要求。舰长日志应包含:
舰长日志模板参考 references/admiralty-templates/captains-log.md,战报提及标准参考 references/commendations.md。
任务完成关卡: 在 captains-log.md 存在于磁盘上并确认可读之前,您不得宣布任务完成。如果上下文压力很大,可以撰写一份简短的日志,注明哪些部分被省略——但文件必须存在。绝不允许跳过第 6 步。
查阅与情况匹配的特定常备指令。
| 情况 | 常备指令 |
|---|---|
| 在单会话和多智能体之间选择 | references/standing-orders/becalmed-fleet.md |
| 决定是否添加另一个智能体 | references/standing-orders/crew-without-canvas.md |
| 在作战计划中为智能体分配文件 | references/standing-orders/split-keel.md |
| 子任务范围偏离航行指令 | references/standing-orders/drifting-anchorage.md |
| 海军上将执行实施工作而非协调 | references/standing-orders/admiral-at-the-helm.md |
| 为红队领航员分配工作 | references/standing-orders/press-ganged-navigator.md |
| 子任务进行时没有风险等级分类 | references/standing-orders/unclassified-engagement.md |
| 舰长执行实施工作而非协调船员 | references/standing-orders/captain-at-the-capstan.md |
| 无论任务需求如何都为每个角色配备船员 | references/standing-orders/all-hands-on-deck.md |
| 为一个原子任务生成一名船员 | references/standing-orders/skeleton-crew.md |
| 分配超出船员角色的工作 | references/standing-orders/pressed-crew.md |
| 舰长部署陆战队执行船员工作或持续任务 | references/standing-orders/battalion-ashore.md |
| 舰长完成自主工作,需要人工操作才能继续 | references/standing-orders/awaiting-admiralty.md |
| 智能体完成任务,依赖图中没有剩余工作 | references/standing-orders/paid-off.md |
查阅与情况匹配的特定程序。
| 情况 | 程序 |
|---|---|
| 智能体无响应、循环或未产生有用输出 | references/damage-control/man-overboard.md |
| 会话中断(上下文限制、崩溃、超时) | references/damage-control/session-resumption.md |
| 发现已完成的任务有缺陷,其他任务正常 | references/damage-control/partial-rollback.md |
| 任务无法成功,继续会浪费预算 | references/damage-control/scuttle-and-reform.md |
| 问题超出当前权限或需要澄清 | references/damage-control/escalation.md |
| 舰船船员消耗不成比例的 token 或时间 | references/damage-control/crew-overrun.md |
| 舰船上下文窗口耗尽,需要替换 | references/damage-control/relief-on-station.md |
| 舰船上下文窗口接近极限 | references/damage-control/hull-integrity.md |
| 使用先前任务的陈旧数据开始新会话 | references/damage-control/session-hygiene.md |
references/standing-orders/admiral-at-the-helm.md 以确认您处于协调角色。每周安装量
1.2K
仓库
GitHub 星标数
198
首次出现
2026 年 2 月 13 日
安全审计
安装于
gemini-cli940
github-copilot940
codex940
opencode940
kimi-cli939
amp939
Execute this workflow for the user's mission.
outcome, metric, and deadline.You MUST read references/admiralty-templates/sailing-orders.md and use the sailing-orders template when the user does not provide structure.
Example sailing orders summary:
Outcome: Refactor auth module to use JWT tokens
Metric: All 47 auth tests pass, no new dependencies
Deadline: This session
Constraints: Do not modify the public API surface
Out of scope: Migration script for existing sessions
Session Hygiene: Before forming the squadron, execute session hygiene per references/damage-control/session-hygiene.md. Clear stale damage reports and turnover briefs from any previous session. Skip this step when resuming an interrupted session.
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.1 admiral + 3-6 captains.1 red-cell navigator for medium/high threat work.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).references/crew-roles.md.Reference references/squadron-composition.md for selection rules and references/crew-roles.md for ship naming and crew composition. Consult the Standing Orders table below before forming the squadron.
Reference references/admiralty-templates/battle-plan.md for the battle plan template and references/admiralty-templates/ship-manifest.md for the ship manifest. Consult the Standing Orders table below 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.
Admiralty Action List: For each task, consciously mark admiralty-action-required: as yes or no. Then scan the battle plan for tasks marked admiralty-action-required: yes. If any exist, surface an Admiralty Action List to the user before spawning any agents:
ADMIRALTY ACTION LIST — Actions required from Admiralty
1. [Task name]
action: [what you must do]
timing: [before task starts | after task completes]
unblocks: [task name or stand-down]
No action needed now. These will be raised by the captain when each step is reached.
If no tasks are marked admiralty-action-required: yes, omit the list — no noise on routine missions. This list is informational, not a gate. The user acknowledges by continuing the conversation. Squadron formation proceeds immediately after.
Crew Briefing: Spawning and task assignment are two steps. First, spawn each captain with the Agent tool, including a crew briefing from references/admiralty-templates/crew-briefing.md in their prompt. Then create and assign work with TaskCreate + TaskUpdate. Teammates do NOT inherit the lead's conversation context — they start with a clean slate and need explicit mission context. See references/tool-mapping.md for full parameter details by mode.
Turnover Briefs: When a ship is relieved due to context exhaustion, it writes a turnover brief using references/admiralty-templates/turnover-brief.md. See references/damage-control/relief-on-station.md for the full procedure.
TaskList for task states: pending, in_progress, completed.SendMessage to unblock captains or redirect their approach.references/standing-orders/paid-off.md. Only hold a ship if a named re-task trigger in the sailing orders has not yet been evaluated.Example quarterdeck checkpoint:
Status: 3/5 tasks complete, 1 blocked, 1 in progress
Blocker: HMS Resolute waiting on API schema from HMS Swift
Action: Redirect HMS Swift to prioritise schema export
Budget: ~40% tokens consumed, on track
Hull: All ships green
Reference references/tool-mapping.md for coordination tools, references/admiralty-templates/quarterdeck-report.md for the report template, and references/admiralty-templates/damage-report.md for damage report format. Use references/commendations.md for recognition signals and graduated correction. Consult the Standing Orders table below if admiral is doing implementation or tasks are drifting from scope.
references/action-stations.md.references/crew-roles.md and the Standing Orders table below if role violations are detected).references/royal-marines.md. Station 2+ marine deployments require admiral approval.Reference references/admiralty-templates/red-cell-review.md for the red-cell review template. Consult the Standing Orders table below if tasks lack a tier or red-cell is assigned implementation work.
captains-log.md in the mission working directory. The log MUST be written to disk — outputting it to chat only does not satisfy this requirement. The captain's log should contain:
Reference references/admiralty-templates/captains-log.md for the captain's log template and references/commendations.md for Mentioned in Despatches criteria.
Mission Complete Gate: You MUST NOT declare the mission complete until captains-log.md exists on disk and has been confirmed readable. If context pressure is high, write a minimal log noting which sections were abbreviated — but the file must exist. Skipping Step 6 is never permitted.
Consult the specific standing order that matches the situation.
| Situation | Standing Order |
|---|---|
| Choosing between single-session and multi-agent | references/standing-orders/becalmed-fleet.md |
| Deciding whether to add another agent | references/standing-orders/crew-without-canvas.md |
| Assigning files to agents in the battle plan | references/standing-orders/split-keel.md |
| Task scope drifting from sailing orders | references/standing-orders/drifting-anchorage.md |
| Admiral doing implementation instead of coordinating | references/standing-orders/admiral-at-the-helm.md |
Consult the specific procedure that matches the situation.
| Situation | Procedure |
|---|---|
| Agent unresponsive, looping, or producing no useful output | references/damage-control/man-overboard.md |
| Session interrupted (context limit, crash, timeout) | references/damage-control/session-resumption.md |
| Completed task found faulty, other tasks are sound | references/damage-control/partial-rollback.md |
| Mission cannot succeed, continuing wastes budget | references/damage-control/scuttle-and-reform.md |
| Issue exceeds current authority or needs clarification | references/damage-control/escalation.md |
references/standing-orders/admiral-at-the-helm.md to confirm you are in coordination role.Weekly Installs
1.2K
Repository
GitHub Stars
198
First Seen
Feb 13, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
gemini-cli940
github-copilot940
codex940
opencode940
kimi-cli939
amp939
React 组合模式指南:Vercel 组件架构最佳实践,提升代码可维护性
102,200 周安装
references/royal-marines.md and use references/admiralty-templates/marine-deployment-brief.md for the deployment brief.references/model-selection.md before assigning models to the squadron. Apply weight-based model selection to all Agent tool calls and include haiku briefing enhancements for agents assigned to haiku.references/damage-control/hull-integrity.mdreferences/admiralty-templates/quarterdeck-report.md. Do not skip this when hull is Green — compaction can occur at any time and the on-disk report is the only recovery point.TaskList for any tasks with description prefixed [AWAITING-ADMIRALTY]:. If any exist, surface the ask to Admiralty immediately — do not batch to the next checkpoint.TaskList: for any task marked admiralty-action-required: yes in the battle plan that shows status completed, confirm there is a quarterdeck log entry recording admiralty sign-off. If no such entry exists, flag to Admiralty for manual verification — the task may have completed without the intended human step.| Assigning work to the red-cell navigator | references/standing-orders/press-ganged-navigator.md |
| Tasks proceeding without a risk tier classification | references/standing-orders/unclassified-engagement.md |
| Captain implementing instead of coordinating crew | references/standing-orders/captain-at-the-capstan.md |
| Crewing every role regardless of task needs | references/standing-orders/all-hands-on-deck.md |
| Spawning one crew member for an atomic task | references/standing-orders/skeleton-crew.md |
| Assigning crew work outside their role | references/standing-orders/pressed-crew.md |
| Captain deploying marines for crew work or sustained tasks | references/standing-orders/battalion-ashore.md |
| Captain completed autonomous work and needs human action to continue | references/standing-orders/awaiting-admiralty.md |
| Agent completed task with no remaining work in the dependency graph | references/standing-orders/paid-off.md |
| Ship's crew consuming disproportionate tokens or time | references/damage-control/crew-overrun.md |
| Ship's context window depleted, needs replacement | references/damage-control/relief-on-station.md |
| Ship context window approaching limits | references/damage-control/hull-integrity.md |
| Starting a new session with stale data from a previous mission | references/damage-control/session-hygiene.md |