跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

deliberation

Multi-perspective synthesis structure — Innovator (propose) → Devil-Advocate (challenge) → Mediator (synthesize) 3-layer execution. Outputs conditional verdicts without binary win/loss. Activates on "deliberation", "battle this out", "weigh the pros and cons", "review from multiple angles", "which side is right?". Optional deep-insight persona jurors for domain-specific views. Designed for design decisions, skill proposals, and architectural choices.

chrono-meta · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add chrono-meta/forge-harness --skill deliberation

技能说明


name: deliberation description: Multi-perspective synthesis structure — Innovator (propose) → Devil-Advocate (challenge) → Mediator (synthesize) 3-layer execution. Outputs conditional verdicts without binary win/loss. Activates on "deliberation", "battle this out", "weigh the pros and cons", "review from multiple angles", "which side is right?". Optional deep-insight persona jurors for domain-specific views. Designed for design decisions, skill proposals, and architectural choices. user-invocable: true allowed-tools: ["Read", "Bash", "Agent"] model-note: session-inherit — Sonnet base is first-class (sonnet_floor_doctrine.md); depth-critical judged steps route to dispatch (opus agent / cross-family sidecar, consent-gated), never a substrate requirement origin: fh-meta

deliberation — The Forge Skill

Innovator (propose) → Devil (challenge) → Mediator (synthesize) 3-layer core structure. The goal is not to pick a winner — it is to extract salvageable fragments from the losing argument and produce a conditional verdict. Even those who struggle to challenge assumptions can use this structure as a rope to reach better decisions.

Role distinction from sim-conductor and steel-quench

  • sim-conductor: validates quality and consistency of a completed asset
  • steel-quench: adversarially stress-tests a near-complete artifact (post-build defect surfacing)
  • deliberation: perspective clash during the design decision process → synthesis (upstream of both)

Triggers

  • /deliberation
  • "battle this out", "make them argue", "clash and synthesize"
  • "review this decision from multiple angles"
  • When agent-composer Step 4-b proposes Wave next-D automatically

Natural Language Triggers (for general users — activates without internal vocabulary)

Also activates when design decisions or perspective clashes are expressed in natural language:

Example phraseIntent
"I'm not sure whether to do this or not"Decision uncertainty → multi-perspective synthesis
"It seems like opinions are divided"Perspective clash → synthesis layer needed
"Help me decide which side is right"Conditional synthesis, not simple winner selection
"Someone will probably object to this"Request for devil's advocate perspective
"Is it okay to keep going in this direction?"Re-validation of design decision
"Review this from multiple angles"Multi-perspective synthesis → 3-layer default
"Analyze this from all sides"Multi-perspective synthesis → 3-layer default
"Weigh the pros and cons"Perspective clash → devil + innovator engaged
"Analyze the strengths and weaknesses"Pro/con structure → Innovator (pros) + Devil (cons)
"Help me make a decision"Decision support → conditional verdict generation
"pros and cons", "pros cons"Comparative analysis → synthesis layer needed

Step 0. Receive Topic + Select Layer

If no input is provided, ask:

Please provide the deliberation topic.
  - Topic: What are you trying to decide or design?
  - Layer: [3-layer default (recommended)] / [5-layer — includes jury]
  - Jury focus (if 5-layer selected): user experience / technical feasibility / business & policy

Default: 3-layer (Innovator → Devil → Mediator). Use 5-layer only when a jury is needed.

Execution log (workers_approved pattern): Upon completing Step 0, include the following in the output:

[DELIBERATION START] Topic: {topic} | Layer: {layer} | {timestamp}
  → WORKER_CALL: Innovator (isolated instance)
  → WORKER_CALL: Devil-Advocate (isolated instance)
  → WORKER_CALL: Mediator (isolated instance — Cost of Consensus prevention)

Jury auto-selection criteria:

Topic natureRecommended jury personas
New user experience relatedbeginner + main-player
Technical implementation feasibilitypersona-be + persona-fe
Business viability / policy / legalpersona-pm + persona-business
General design decisionsNo jury (3-layer is sufficient)

Step 1. Innovator Layer — Propose

Invoke deep-insight:persona-innovator.

Fallback (if deep-insight is not installed): Claude Code performs the Innovator role inline. Same instruction template and output format apply. The deliberation pipeline is guaranteed to work without deep-insight installed.

No isolation (intentional): The Innovator is a proposal generator — it does not evaluate its own output, so Agent tool isolation is not needed. Cost of Consensus applies only to the Mediator, which evaluates its own generated content (arXiv 2605.00914). Only the Mediator (Step 3) is isolated via the Agent tool.

Instruction template (meta-prompt-builder structure):

Goal: Generate the most creative and scalable proposals for {topic}
Context: Current harness state + list of relevant assets
Constraints: No duplication of existing assets / must not violate simplification guard
Done When: 1~3 concrete proposals + 1-line rationale per proposal
Brief limit: Total Context passed to Agent must be kept under 1200 characters

Output format:

[Innovator]
  Proposal 1: {content} — Rationale: {1 line}
  Proposal 2: {content} — Rationale: {1 line}
  (optional) Proposal 3: {content} — Rationale: {1 line}

Step 2. Devil-Advocate Layer — Challenge

Invoke deep-insight:persona-devil-advocate. Takes Step 1 output as input.

Fallback (if deep-insight is not installed): fh-commons:quench-challenger (includes Devil DNA) or Claude Code performs the Devil-Advocate role inline. Same output format. Instance isolation is not required, same as Step 1.

Instruction template:

Goal: Generate the sharpest single rebuttal for each of the {N} Innovator proposals
Context: Innovator output + harness simplification guard + known failure patterns
Constraints: No emotional rebuttals / no baseless negation / must include a hint toward improvement
Done When: 1 rebuttal per proposal + 1-line core 
阅读完整来源 ↗