pov-expansion

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

POV-Expansion: Cross-Domain Perspective Generation

POV-Expansion:跨领域视角生成

Generate systematic cross-domain perspectives through boundary spanning research frameworks. Uses structure-mapping theory, convergence tracking, and transfer evaluation to identify analogous problems and transferable solutions.
通过跨边界研究框架生成系统化的跨领域视角。利用结构映射理论、趋同性追踪和迁移评估来识别类似问题和可迁移的解决方案。

When to Use

适用场景

Use this skill when:
  • Stuck on a problem - Need fresh perspectives from outside your domain
  • Evaluating analogies - Want to assess if approach from field X applies to field Y
  • Seeking breakthrough insights - Ready for 2-3 hour deep exploration
  • Have structured problem - Can articulate problem clearly enough for abstraction
在以下场景中使用此技能:
  • 遇到问题瓶颈 - 需要来自你所在领域之外的全新视角
  • 评估类比方案 - 想要判断X领域的方法是否适用于Y领域
  • 寻求突破性见解 - 准备进行2-3小时的深度探索
  • 拥有结构化问题 - 能够清晰地阐述问题以进行抽象提炼

When NOT to Use

不适用场景

Do NOT use when:
  • Exploratory browsing - No specific problem statement (use /research-pipeline instead)
  • Time-constrained - Need answer in <1 hour (this workflow takes 2-3 hours minimum)
  • Well-understood problem - Already know the solution domain (direct research faster)
  • Vague problem - Cannot articulate problem clearly (refine first)
请勿在以下场景中使用:
  • 探索性浏览 - 没有具体的问题陈述(请改用/research-pipeline)
  • 时间紧张 - 需要在1小时内得到答案(此工作流至少需要2-3小时)
  • 问题已明确 - 已经了解解决方案领域(直接研究效率更高)
  • 问题模糊 - 无法清晰阐述问题(请先细化问题)

Architecture

架构

Three-tier architecture:
  1. Orchestrator: pov-expansion-pm (coordinates workflow, handles exceptions)
  2. Specialist Agents: 5 new agents for abstraction, perspective generation, synthesis, transfer evaluation
  3. Supporting Skills: Reuses requirements-analyst, fact-checker, devils-advocate, editor, strategist
三层架构
  1. 编排器:pov-expansion-pm(协调工作流,处理异常)
  2. 专业Agent:5个用于抽象提炼、视角生成、综合分析、迁移评估的新Agent
  3. 支持技能:复用requirements-analyst、fact-checker、devils-advocate、editor、strategist

Pre-flight Validation

启动前验证

Before invoking
/pov-expansion
, verify:
  • Problem statement is specific (not "improve product" but "reduce onboarding time")
  • Expected runtime: 2-3 hours (workflow cannot be rushed)
  • Dependencies available: requirements-analyst, fact-checker, devils-advocate, editor, strategist skills exist
在调用
/pov-expansion
之前,请确认:
  • 问题陈述具体明确(不是“改进产品”,而是“减少用户注册流程耗时”)
  • 预期运行时间:2-3小时(工作流无法加速)
  • 依赖项可用:requirements-analyst、fact-checker、devils-advocate、editor、strategist技能已存在

The 12-Stage Pipeline

12阶段工作流

Stage 0: Archival Guidelines Review

阶段0:归档指南审查

Owner: pov-expansion-pm (automatic) Duration: 2-5 min Checkpoint: Never (always runs automatically) Session Setup: Creates
/tmp/pov-session-{YYYYMMDD-HHMMSS}-{PID}/
Initialize workflow session and extract archival guidelines from project CLAUDE.md.
Process:
  1. Create session directory:
    /tmp/pov-session-$(date +%Y%m%d-%H%M%S)-$$/
  2. Read project CLAUDE.md (if exists in working directory or parent)
  3. Extract archival guidelines:
    • Repository organization (directory structure for cross-domain analyses)
    • Naming conventions (
      analysis-
      prefix for POV expansion outputs)
    • Git rules (commit after edits, no version-numbered files)
    • Document structure requirements (Executive Summary, Key Parameters Table)
    • Citation format (Nature-style inline)
  4. Write archival summary to session directory:
    archival-guidelines-summary.md
  5. Store session path in workflow state for downstream agents
Output:
yaml
session_setup:
  session_dir: "/tmp/pov-session-{timestamp}-{pid}/"
  archival_summary_path: "{session_dir}/archival-guidelines-summary.md"
  guidelines_found: boolean
  guidelines_source: string  # Path to CLAUDE.md or "defaults"
Quality Gate: Session directory created, archival summary written.
Failure Handling:
  • CLAUDE.md not found: Use sensible defaults, log warning
  • Session directory creation fails: ABORT (cannot proceed without session isolation)
负责人:pov-expansion-pm(自动执行) 时长:2-5分钟 检查点:无(始终自动运行) 会话设置:创建
/tmp/pov-session-{YYYYMMDD-HHMMSS}-{PID}/
目录
初始化工作流会话,并从项目CLAUDE.md中提取归档指南。
流程
  1. 创建会话目录
    /tmp/pov-session-$(date +%Y%m%d-%H%M%S)-$$/
  2. 读取项目CLAUDE.md(如果存在于工作目录或父目录中)
  3. 提取归档指南
    • 仓库组织(跨领域分析的目录结构)
    • 命名规范(POV扩展输出使用
      analysis-
      前缀)
    • Git规则(编辑后提交,不使用带版本号的文件)
    • 文档结构要求(执行摘要、关键参数表)
    • 引用格式(Nature风格的内联引用)
  4. 将归档摘要写入会话目录
    archival-guidelines-summary.md
  5. 将会话路径存储到工作流状态,供下游Agent使用
输出
yaml
session_setup:
  session_dir: "/tmp/pov-session-{timestamp}-{pid}/"
  archival_summary_path: "{session_dir}/archival-guidelines-summary.md"
  guidelines_found: boolean
  guidelines_source: string  # Path to CLAUDE.md or "defaults"
质量门:会话目录已创建,归档摘要已写入。
故障处理
  • 未找到CLAUDE.md:使用合理默认值,记录警告
  • 会话目录创建失败:终止(无会话隔离无法继续)

Stage 1: Problem Refinement

阶段1:问题细化

Owner: requirements-analyst (reused) Duration: 15-30 min Receives: Session directory path from Stage 0 Quality Gate: Specific problem statement with measurable criteria
负责人:requirements-analyst(复用) 时长:15-30分钟 接收输入:阶段0的会话目录路径 质量门:包含可衡量标准的具体问题陈述

Stage 2: Problem Abstraction

阶段2:问题抽象

Owner: pov-abstractor-classifier Duration: 15-30 min Quality Gate: Rasmussen hierarchy populated (5/5 levels)
负责人:pov-abstractor-classifier 时长:15-30分钟 质量门:完整填充Rasmussen层级(5个层级全部完成)

Stage 3: Domain Classification

阶段3:领域分类

Owner: pov-abstractor-classifier Duration: 20-45 min (includes user confirmation) Quality Gate: 4 domains proposed (1+ Near, 1+ Mid, 1+ Far), user confirmed
负责人:pov-abstractor-classifier 时长:20-45分钟(包含用户确认时间) 质量门:提出4个领域(至少1个近领域、1个中领域、1个远领域),并获得用户确认

Stage 4: Parallel Perspective Generation

阶段4:并行视角生成

Owner: pov-perspective-analyst (x4 parallel) Duration: 30-60 min (parallel) Quality Gate: 3+ perspectives complete, each with structural analogies
负责人:pov-perspective-analyst(4个并行执行) 时长:30-60分钟(并行执行) 质量门:完成至少3个视角,每个视角包含结构类比

Stage 5: Parallel Verification

阶段5:并行验证

Owner: fact-checker (x2 parallel, reused) Duration: 15-30 min (parallel) Quality Gate: No factual errors in central claims
负责人:fact-checker(2个并行执行,复用) 时长:15-30分钟(并行执行) 质量门:核心主张无事实错误

Stage 6: Convergence Analysis

阶段6:趋同性分析

Owner: pov-synthesizer Duration: 20-40 min Quality Gate: Convergence floor met (1+ theme in 2+ reports)
负责人:pov-synthesizer 时长:20-40分钟 质量门:达到趋同性阈值(至少1个主题出现在2份以上报告中)

Stage 7: Transfer Evaluation

阶段7:迁移评估

Owner: pov-transfer-evaluator Duration: 20-40 min Quality Gate: Transfer feasibility scored, Far field warnings added
负责人:pov-transfer-evaluator 时长:20-40分钟 质量门:完成迁移可行性评分,并添加远领域警告

Stage 8: Master Synthesis

阶段8:主综合分析

Owner: pov-synthesizer Duration: 45-90 min Quality Gate: All perspectives integrated, convergent insights highlighted
负责人:pov-synthesizer 时长:45-90分钟 质量门:整合所有视角,突出趋同性见解

Stage 9: Strategic Assessment

阶段9:战略评估

Owner: strategist (reused skill) Duration: 20-40 min Quality Gate: 3+ actionable recommendations with implementation paths
负责人:strategist(复用技能) 时长:20-40分钟 质量门:提出至少3个可落地的建议及实施路径

Stage 10: Adversarial Review

阶段10:对抗性审查

Owner: devils-advocate (reused) Duration: 20-40 min Quality Gate: Critical issues identified, mitigations proposed
负责人:devils-advocate(复用) 时长:20-40分钟 质量门:识别关键问题,并提出缓解方案

Stage 11: Editorial Polish

阶段11:编辑润色

Owner: editor (reused) Duration: 15-30 min Quality Gate: Consistent voice, no substantive errors
负责人:editor(复用) 时长:15-30分钟 质量门:语气一致,无实质性错误

Timeout Configuration

超时配置

StageTimeoutExceeded Action
0 (Archival)5 minABORT - cannot proceed without session
1 (Refinement)30 minEscalate to user
2 (Abstraction)30 minEscalate to user
3 (Classification)45 minProceed with HIGH confidence domains only
4 (Perspectives)60 min totalProceed with available (minimum 2 required)
4 (per agent)20 minRetry once, then skip
5 (Verification)30 minSkip verification (flag risk)
6 (Convergence)40 minProceed with portfolio framing
7 (Transfer)40 minLower confidence, proceed
8 (Synthesis)90 minEscalate to user
9 (Strategic)40 minSkip (optional)
10 (Review)40 minDeliver without review (flag risk)
11 (Editorial)30 minDeliver as-is, cleanup session
Global Workflow Timeout: 8 hours On Global Timeout: Save state, escalate to user
Session Cleanup:
  • On successful completion (Stage 11 complete): Delete session directory
  • On failure/abort: Retain session directory for debugging (log path to user)
阶段超时时间超时动作
0(归档)5分钟终止 - 无会话无法继续
1(细化)30分钟升级给用户处理
2(抽象)30分钟升级给用户处理
3(分类)45分钟仅使用高置信度领域继续
4(视角生成)总计60分钟使用已完成的视角继续(至少需要2个)
4(单个Agent)20分钟重试一次,然后跳过
5(验证)30分钟跳过验证(标记风险)
6(趋同性分析)40分钟继续并采用组合框架
7(迁移评估)40分钟降低置信度,继续执行
8(综合分析)90分钟升级给用户处理
9(战略评估)40分钟跳过(可选阶段)
10(审查)40分钟直接交付,不进行审查(标记风险)
11(编辑)30分钟按原样交付,清理会话
全局工作流超时:8小时 全局超时动作:保存状态,升级给用户处理
会话清理
  • 成功完成(阶段11完成):删除会话目录
  • 失败/终止:保留会话目录用于调试(将会话路径告知用户)

Quality Gate Specifications

质量门规范

Gate 0: Session Initialization (Stage 0)

门0:会话初始化(阶段0)

CheckThresholdAutomated?
Session directory createdexists and writableYes
Archival summary writtenfile existsYes
Session path stored in workflow statepath presentYes
Pass Threshold: 3/3 checks pass On Failure: ABORT - cannot proceed without session isolation
检查项阈值自动化?
会话目录已创建存在且可写入
归档摘要已写入文件存在
会话路径已存储到工作流状态路径已存在
通过阈值:3项检查全部通过 失败动作:终止 - 无会话隔离无法继续

Gate 1: Problem Abstraction (Stage 2)

门1:问题抽象(阶段2)

CheckThresholdAutomated?
Rasmussen levels populated5/5 levelsYes
Structural elements identified>= 3 elementsYes
Constraints defined>= 1 constraintYes
Success metrics measurable>= 1 metricManual
Pass Threshold: 4/4 checks pass On Failure: Return to Stage 1 with feedback (max 2 iterations)
检查项阈值自动化?
Rasmussen层级已填充5个层级全部完成
已识别结构元素至少3个元素
已定义约束条件至少1个约束
成功指标可衡量至少1个指标手动
通过阈值:4项检查全部通过 失败动作:返回阶段1并提供反馈(最多2次迭代)

Gate 2: Domain Classification (Stage 3)

门2:领域分类(阶段3)

CheckThresholdAutomated?
Domains proposed4 domainsYes
Near field present>= 1Yes
Far field present>= 1Yes
User confirmationRequiredNo
Pass Threshold: All checks pass On Failure: Re-run with user guidance
检查项阈值自动化?
已提出领域4个领域
包含近领域至少1个
包含远领域至少1个
用户确认必需
通过阈值:所有检查项通过 失败动作:在用户指导下重新运行

Gate 3: Perspective Generation (Stage 4)

门3:视角生成(阶段4)

CheckThresholdAutomated?
Perspectives complete>= 3 of 4Yes
Structural analogies per perspective>= 2Yes
Domain-specific examples>= 2 per perspectiveYes
No placeholder text0 instancesYes
Pass Threshold: All checks pass Marginal Pass: 3/4 checks (flag in synthesis) On Failure: Retry failed perspective or proceed with reduced coverage
检查项阈值自动化?
视角已完成至少4个中的3个
每个视角包含结构类比至少2个
领域特定示例每个视角至少2个
无占位文本0个实例
通过阈值:所有检查项通过 边际通过:4项中的3项(在综合分析中标记) 失败动作:重试失败的视角,或减少覆盖范围继续执行

Gate 4: Transfer Feasibility (Stage 7)

门4:迁移可行性(阶段7)

CheckThresholdAutomated?
All perspectives evaluated100%Yes
Structural similarity scoredAll have scoresYes
At least one high-transfer analogy>= 1 with score > 0.6Yes
Far field warnings addedAll Far field have warningsYes
Pass Threshold: 4/4 checks pass Marginal Pass: 3/4 (proceed with caution flag) On Failure: Return to Stage 3 with broadened domains
检查项阈值自动化?
所有视角已评估100%
已对结构相似性评分所有视角均有评分
至少1个高迁移性类比至少1个评分>0.6
已添加远领域警告所有远领域均有警告
通过阈值:4项检查全部通过 边际通过:4项中的3项(标记为谨慎执行) 失败动作:返回阶段3,扩大领域范围

Gate 5: Synthesis Coherence (Stage 8)

门5:综合分析连贯性(阶段8)

CheckThresholdAutomated?
All perspectives referenced100%Yes
Convergent insights highlighted>= 1Yes
Contradictions resolved0 unresolvedManual
Executive summary presentYesYes
Pass Threshold: All checks pass On Failure: Return to synthesis with feedback
检查项阈值自动化?
所有视角已引用100%
已突出趋同性见解至少1个
矛盾已解决0个未解决矛盾手动
存在执行摘要
通过阈值:所有检查项通过 失败动作:返回综合分析阶段并提供反馈

Gate 6: Strategic Actionability (Stage 9)

门6:战略可落地性(阶段9)

CheckThresholdAutomated?
Actionable recommendations>= 3Yes
Implementation pathsEach has pathYes
Timeline/effort estimatesPresentYes
Pass Threshold: All checks pass On Failure: Add missing elements or skip stage
检查项阈值自动化?
可落地建议至少3个
实施路径每个建议都有路径
时间线/工作量估算已提供
通过阈值:所有检查项通过 失败动作:补充缺失元素或跳过此阶段

Session Directory Structure

会话目录结构

Location:
/tmp/pov-session-{YYYYMMDD-HHMMSS}-{PID}/
/tmp/pov-session-{YYYYMMDD-HHMMSS}-{PID}/
├── archival-guidelines-summary.md  # Stage 0 output
├── workflow-state.yaml             # Workflow state for resume
├── progress.md                     # Progress tracking
├── stage-1-refinement.md           # Stage 1 output
├── stage-2-abstraction.yaml        # Stage 2 output (structured)
├── stage-3-domains.yaml            # Stage 3 output (structured)
├── stage-4-perspectives/           # Parallel outputs
│   ├── near-field-1.md
│   ├── near-field-2.md
│   ├── mid-field.md
│   └── far-field.md
├── stage-5-verification/           # Parallel outputs
│   ├── verification-1.md
│   └── verification-2.md
├── stage-6-convergence.md
├── stage-7-transfer.md
├── stage-8-synthesis.md
├── stage-9-strategic.md
├── stage-10-review.md
├── stage-11-final.md               # Final deliverable
└── failure-log.md                  # Failure tracking
位置:
/tmp/pov-session-{YYYYMMDD-HHMMSS}-{PID}/
/tmp/pov-session-{YYYYMMDD-HHMMSS}-{PID}/
├── archival-guidelines-summary.md  # 阶段0输出
├── workflow-state.yaml             # 用于恢复的工作流状态
├── progress.md                     # 进度跟踪
├── stage-1-refinement.md           # 阶段1输出
├── stage-2-abstraction.yaml        # 阶段2输出(结构化)
├── stage-3-domains.yaml            # 阶段3输出(结构化)
├── stage-4-perspectives/           # 并行输出
│   ├── near-field-1.md
│   ├── near-field-2.md
│   ├── mid-field.md
│   └── far-field.md
├── stage-5-verification/           # 并行输出
│   ├── verification-1.md
│   └── verification-2.md
├── stage-6-convergence.md
├── stage-7-transfer.md
├── stage-8-synthesis.md
├── stage-9-strategic.md
├── stage-10-review.md
├── stage-11-final.md               # 最终交付物
└── failure-log.md                  # 故障跟踪

Workflow State Schema

工作流状态 Schema

yaml
workflow_state:
  workflow_id: string
  problem_statement: string
  started_at: ISO8601
  current_stage: integer  # 0-11
  stages_completed: [integer]

  session:                              # Added for session management
    session_dir: string                 # /tmp/pov-session-{...}/
    archival_guidelines_path: string    # Path to archival-guidelines-summary.md
    guidelines_found: boolean           # Whether CLAUDE.md was found
    guidelines_source: string           # Path to CLAUDE.md or "defaults"
    cleanup_on_complete: boolean        # Default true

  artifacts:
    stage_0: path | null                # archival-guidelines-summary.md
    stage_1: path | null
    stage_2: path | null
    # ... etc
    stage_11: path | null

  status: enum[in_progress, paused, completed, failed]
  last_checkpoint: ISO8601
  error_log: [string]
Session Handling on Resume:
  • If session directory exists: Reuse existing session
  • If session directory missing: Re-run Stage 0 to recreate (non-destructive)
yaml
workflow_state:
  workflow_id: string
  problem_statement: string
  started_at: ISO8601
  current_stage: integer  # 0-11
  stages_completed: [integer]

  session:                              # 新增会话管理
    session_dir: string                 # /tmp/pov-session-{...}/
    archival_guidelines_path: string    # archival-guidelines-summary.md的路径
    guidelines_found: boolean           # 是否找到CLAUDE.md
    guidelines_source: string           # CLAUDE.md的路径或"defaults"
    cleanup_on_complete: boolean        # 默认true

  artifacts:
    stage_0: path | null                # archival-guidelines-summary.md
    stage_1: path | null
    stage_2: path | null
    # ... 以此类推
    stage_11: path | null

  status: enum[in_progress, paused, completed, failed]
  last_checkpoint: ISO8601
  error_log: [string]
恢复会话处理
  • 如果会话目录存在:复用现有会话
  • 如果会话目录缺失:重新运行阶段0以创建(非破坏性)

Error Handling Protocols

错误处理协议

Catastrophic Failure Protocol (Stage 4)

灾难性故障协议(阶段4)

When ALL perspective agents fail:
  1. Detection: 0 valid outputs from 4 parallel agents
  2. Check for partial outputs: Any content > 500 chars is "partial"
  3. Present user options:
PERSPECTIVE GENERATION FAILED: All 4 agents failed

Failures:
- Near Field 1: [status]
- Near Field 2: [status]
- Mid Field: [status]
- Far Field: [status]

Options:
(A) Retry SEQUENTIALLY (slower but more stable)
(B) Retry with 2 agents only (Near + Mid fields)
(C) Review partial outputs if available
(D) Abort workflow, preserve problem abstraction
当所有视角Agent都失败时:
  1. 检测:4个并行Agent均无有效输出
  2. 检查部分输出:任何内容超过500字符视为“部分输出”
  3. 向用户提供选项
视角生成失败:所有4个Agent均失败

失败情况:
- 近领域1:[状态]
- 近领域2:[状态]
- 中领域:[状态]
- 远领域:[状态]

选项:
(A) 顺序重试(速度较慢但更稳定)
(B) 仅重试2个Agent(近领域+中领域)
(C) 查看可用的部分输出
(D) 终止工作流,保留问题抽象结果

Convergence Floor Protocol

趋同性阈值协议

Minimum Convergence Threshold:
  • 1+ themes appearing in 2+ reports, OR
  • 2+ strategies appearing in 2+ reports, OR
  • 1+ structural analogies across 2+ domains
On Zero Convergence:
  1. Re-analyze with relaxed matching (related concepts, not exact)
  2. Look for "anti-convergence" (all agree something doesn't work)
  3. If still zero: Offer portfolio framing (present as independent options, not validated patterns)
最小趋同性阈值
  • 至少1个主题出现在2份以上报告中,或
  • 至少2个策略出现在2份以上报告中,或
  • 至少1个结构类比跨2个以上领域
无趋同性情况
  1. 使用宽松匹配重新分析(相关概念,而非完全一致)
  2. 寻找“反趋同性”(所有视角均认为某方法不可行)
  3. 若仍无趋同性:采用组合框架(作为独立选项呈现,而非已验证的模式)

User Response Timeout Protocol

用户响应超时协议

GateTimeoutDefault Action
Domain Classification10 minProceed with HIGH confidence domains only
Transfer Feasibility5 minProceed with portfolio view
Strategic Priority5 minPresent all options without prioritization
质量门超时时间默认动作
领域分类10分钟仅使用高置信度领域继续
迁移可行性5分钟继续并采用组合视图
战略优先级5分钟呈现所有选项,不进行优先级排序

Parallel Execution

并行执行

Stage 4: Perspective Generation (Fork-Join)

阶段4:视角生成(分叉-合并)

yaml
parallel_execution:
  stage: 4
  pattern: fork_join
  max_agents: 4

  agent_assignment:
    agent_1: "Near Field 1"
    agent_2: "Near Field 2"
    agent_3: "Mid Field"
    agent_4: "Far Field"

  output_paths:
    agent_1: "/tmp/pov-session-{id}/stage-4-perspectives/near-field-1.md"
    agent_2: "/tmp/pov-session-{id}/stage-4-perspectives/near-field-2.md"
    agent_3: "/tmp/pov-session-{id}/stage-4-perspectives/mid-field.md"
    agent_4: "/tmp/pov-session-{id}/stage-4-perspectives/far-field.md"

  completion:
    minimum_required: 2
    proceed_on_timeout: true
    log_missing: true
yaml
parallel_execution:
  stage: 4
  pattern: fork_join
  max_agents: 4

  agent_assignment:
    agent_1: "Near Field 1"
    agent_2: "Near Field 2"
    agent_3: "Mid Field"
    agent_4: "Far Field"

  output_paths:
    agent_1: "/tmp/pov-session-{id}/stage-4-perspectives/near-field-1.md"
    agent_2: "/tmp/pov-session-{id}/stage-4-perspectives/near-field-2.md"
    agent_3: "/tmp/pov-session-{id}/stage-4-perspectives/mid-field.md"
    agent_4: "/tmp/pov-session-{id}/stage-4-perspectives/far-field.md"

  completion:
    minimum_required: 2
    proceed_on_timeout: true
    log_missing: true

Stage 5: Verification (Parallel)

阶段5:验证(并行)

yaml
parallel_execution:
  stage: 5
  pattern: parallel
  max_agents: 2

  assignment:
    agent_1: "Near + Mid perspectives"
    agent_2: "Far perspective + cross-check"
yaml
parallel_execution:
  stage: 5
  pattern: parallel
  max_agents: 2

  assignment:
    agent_1: "Near + Mid perspectives"
    agent_2: "Far perspective + cross-check"

Success Criteria

成功标准

  • Diversity: Perspectives span Near, Mid, and Far fields (4 domains minimum)
  • Depth: Structural analogies via structure-mapping principles (>=2 per perspective)
  • Convergence: Cross-perspective insights tracked with measurable algorithm
  • Transferability: Rigorous transfer evaluation with Far field warnings
  • Actionability: Strategic assessment with >=3 recommendations and implementation paths
  • 多样性:视角覆盖近、中、远领域(至少4个领域)
  • 深度:基于结构映射原则的结构类比(每个视角至少2个)
  • 趋同性:使用可量化算法跟踪跨视角见解
  • 可迁移性:严格的迁移评估,包含远领域警告
  • 可落地性:战略评估包含至少3个建议及实施路径