技能委员会
- 作者仓库星标 3,406
- 作者仓库 claude-octopus
- 领域
- 人工智能
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @nyldn · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第 0 阶段:预检
收集或推断:目标:`advice`、`decision`、`plan`、`implement`或`review`域:`auto`、`architecture`、`product`、`security`, `business`、`research`或`docs` 样式:`balanced`、`adversarial`、`implementation`、`executive`或`red-team` 深度:`quick`、`standard`或`deep`
# Council
Use this skill for `/octo:council` and council-style requests.
## Phase 0: Preflight
Collect or infer:
- goal: `advice`, `decision`, `plan`, `implement`, or `review`
- domain: `auto`, `architecture`, `product`, `security`, `business`, `research`, or `docs`
- style: `balanced`, `adversarial`, `implementation`, `executive`, or `red-team`
- depth: `quick`, `standard`, or `deep`
- members: `auto`, `3`, `5`, or `7`
- budget cap in USD
- providers and provider availability
- pinned personas
- implementation permission and worktree isolation
Show the selected council, provider availability, benchmark freshness, quorum requirement, and cost estimate before provider fanout. Re-check the budget before critique, revision, synthesis, and implementation planning so the run stops before the next phase would exceed `--max-cost`. If the run is a dry run, stop after this preflight and write `summary.json`.
## Quorum
- quick requires at least one non-chair response plus a synthesis-capable chair
- standard and deep require at least two non-chair responses plus a synthesis-capable chair
- if the chair fails, retry once with the highest-scoring synthesis-capable fallback
- if quorum is lost, stop by default and present partial artifacts instead of pretending consensus exists
## Council Procedure
1. **Independent advice:** ask each selected persona for recommendation, assumptions, risks, implementation notes, and confidence.
2. **Cross-critique:** for standard/deep runs, semi-anonymize responses and ask members to critique gaps, assumptions, and risks.
3. **Revision:** for deep runs or high disagreement, let members revise their positions after critique.
4. **Chair synthesis:** produce agreement, disagreement, minority reports, risk register, implementation path, confidence, and conditions that would change the recommendation.
5. **Ratify / veto:** verifier, red-team, security, legal, finance, and medical roles can veto implementation for critical risks.
## Implementation Gates
- **Gate A:** user accepts the council synthesis or asks for revision.
- **Gate B:** user accepts the concrete implementation plan generated from the synthesis.
- **Gate C:** execution proceeds through existing Octopus implementation safety behavior. This is a one-shot authorization for the accepted plan, not per-file approval, unless existing safety hooks detect destructive or risky actions.
Never implement from council output without explicit approval. Preserve disagreement, summarize risks, and keep vetoes visible in the final answer and artifacts.
章节与文件索引
按说明文件中的顺序排列。
第 0 阶段:预检
法定人数
理事会程序
实施门
文件/命令 -> /octo:council · advice · decision · plan · implement · review · auto · architecture
内容校验值 -> 6f4726da57ef
当前原文的自动摘译,尚未人工审校。
第 0 阶段:预检
收集或推断:目标:
advice、decision、plan、implement或review域:auto、architecture、product、security、business,research或docs样式:balanced、adversarial、implementation、executive或red-team深度:quick、standard或deep法定人数
快速需要至少一个非主席响应加上一个能够综合的主席标准,深度需要至少两个非主席响应加上一个能够综合的主席(如果主席失败),如果法定人数丢失,则使用得分最高的综合能力后备重试一次,默认停止并呈现部分工件,而不是假装存在共识
理事会程序
独立建议:向每个选定的角色询问建议、假设、风险、实施说明和信心。交叉批评:对于标准/深度运行,半匿名回复并要求成员批评差距、假设和风险。修正:对于深度分歧或高度分歧的情况,让成员在批评后修正自己的立场。主席综合:提出同意、分歧、少数派报告、风险登记册、实施路径、信心和会改变建议的条件。
实施门
A 门:用户接受理事会综合报告或要求修改。 Gate B:用户接受综合生成的具体实施计划。 Gate C:通过现有的八达通实施安全行为继续执行。这是对已接受计划的一次性授权,而不是针对每个文件的批准,除非现有安全挂钩检测到破坏性或危险行为。未经明确批准,切勿实施理事会的产出。保留分歧,总结风险,并在最终答案和工件中保留否决权。