meta-cognition-parallel
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseMeta-Cognition Parallel Analysis (Experimental)
三层并行元认知分析(实验性)
Status: Experimental | Version: 0.1.0This skill tests parallel three-layer cognitive analysis using.context: fork
状态: 实验性 | 版本: 0.1.0本Skill使用测试三层认知并行分析。context: fork
Concept
概念
Instead of sequential analysis, this skill launches three parallel subagents - one for each cognitive layer - then synthesizes their results.
User Question
│
▼
┌─────────────────────────────────────────────────────┐
│ meta-cognition-parallel │
│ (Coordinator) │
└─────────────────────────────────────────────────────┘
│
├─── Task(fork) ──► layer1-analyzer ──► L1 Result
│ (Language Mechanics)
│
├─── Task(fork) ──► layer2-analyzer ──► L2 Result
│ (Design Choices) ├── Parallel
│ │
└─── Task(fork) ──► layer3-analyzer ──► L3 Result
(Domain Constraints)
│
▼
┌─────────────────────────────────────────────────────┐
│ Cross-Layer Synthesis │
│ (In main context with all results) │
└─────────────────────────────────────────────────────┘
│
▼
Domain-Correct Architectural Solution与顺序分析不同,本Skill会启动三个并行的子代理(subagent)——对应每个认知层级——然后综合它们的结果。
User Question
│
▼
┌─────────────────────────────────────────────────────┐
│ meta-cognition-parallel │
│ (Coordinator) │
└─────────────────────────────────────────────────────┘
│
├─── Task(fork) ──► layer1-analyzer ──► L1 Result
│ (Language Mechanics)
│
├─── Task(fork) ──► layer2-analyzer ──► L2 Result
│ (Design Choices) ├── Parallel
│ │
└─── Task(fork) ──► layer3-analyzer ──► L3 Result
(Domain Constraints)
│
▼
┌─────────────────────────────────────────────────────┐
│ Cross-Layer Synthesis │
│ (In main context with all results) │
└─────────────────────────────────────────────────────┘
│
▼
Domain-Correct Architectural SolutionUsage
使用方法
/meta-parallel <your Rust question>Example:
/meta-parallel 我的交易系统报 E0382 错误,应该用 clone 吗?/meta-parallel <你的Rust问题>示例:
/meta-parallel 我的交易系统报 E0382 错误,应该用 clone 吗?Execution Instructions
执行说明
Step 1: Parse User Query
步骤1:解析用户查询
Extract from :
$ARGUMENTS- The original question
- Any code snippets
- Domain hints (trading, web, embedded, etc.)
从中提取:
$ARGUMENTS- 原始问题
- 所有代码片段
- 领域提示(交易、Web、嵌入式等)
Step 2: Launch Three Parallel Agents
步骤2:启动三个并行代理
CRITICAL: Launch all three Tasks in a SINGLE message to enable parallel execution.
Read agent files, then launch in parallel:
Task(
subagent_type: "general-purpose",
run_in_background: true,
prompt: <content of agents/layer1-analyzer.md>
+ "\n\n## User Query\n" + $ARGUMENTS
)
Task(
subagent_type: "general-purpose",
run_in_background: true,
prompt: <content of agents/layer2-analyzer.md>
+ "\n\n## User Query\n" + $ARGUMENTS
)
Task(
subagent_type: "general-purpose",
run_in_background: true,
prompt: <content of agents/layer3-analyzer.md>
+ "\n\n## User Query\n" + $ARGUMENTS
)关键:在单条消息中启动所有三个Task以启用并行执行。
Read agent files, then launch in parallel:
Task(
subagent_type: "general-purpose",
run_in_background: true,
prompt: <content of agents/layer1-analyzer.md>
+ "\n\n## User Query\n" + $ARGUMENTS
)
Task(
subagent_type: "general-purpose",
run_in_background: true,
prompt: <content of agents/layer2-analyzer.md>
+ "\n\n## User Query\n" + $ARGUMENTS
)
Task(
subagent_type: "general-purpose",
run_in_background: true,
prompt: <content of agents/layer3-analyzer.md>
+ "\n\n## User Query\n" + $ARGUMENTS
)Step 3: Collect Results
步骤3:收集结果
Wait for all three agents to complete. Each returns structured analysis.
等待所有三个代理完成。每个代理都会返回结构化分析结果。
Step 4: Cross-Layer Synthesis
步骤4:跨层综合
With all three results, perform synthesis:
markdown
undefined结合三个结果,执行综合分析:
markdown
undefinedCross-Layer Synthesis
跨层综合分析
Layer Results Summary
各层级结果摘要
| Layer | Key Finding | Confidence |
|---|---|---|
| L1 (Mechanics) | [Summary] | [Level] |
| L2 (Design) | [Summary] | [Level] |
| L3 (Domain) | [Summary] | [Level] |
| 层级 | 关键发现 | 置信度 |
|---|---|---|
| L1(语言机制) | [摘要] | [等级] |
| L2(设计选型) | [摘要] | [等级] |
| L3(领域约束) | [摘要] | [等级] |
Cross-Layer Reasoning
跨层推理
- L3 → L2: [How domain constraints affect design choice]
- L2 → L1: [How design choice determines mechanism]
- L1 ← L3: [Direct domain impact on language features]
- L3 → L2: [领域约束如何影响设计选型]
- L2 → L1: [设计选型如何决定实现机制]
- L1 ← L3: [领域对语言特性的直接影响]
Synthesized Recommendation
综合推荐方案
Problem: [Restated with full context]
Solution: [Domain-correct architectural solution]
Rationale:
- Domain requires: [L3 constraint]
- Design pattern: [L2 pattern]
- Mechanism: [L1 implementation]
问题: [结合完整上下文重述问题]
解决方案: [符合领域要求的架构方案]
理由:
- 领域要求:[L3约束]
- 设计模式:[L2模式]
- 实现机制:[L1实现]
Confidence Assessment
置信度评估
- Overall: HIGH | MEDIUM | LOW
- Limiting Factor: [Which layer had lowest confidence]
undefined- 整体: 高 | 中 | 低
- 限制因素: [哪个层级的置信度最低]
undefinedOutput Template
输出模板
markdown
undefinedmarkdown
undefinedThree-Layer Meta-Cognition Analysis
三层元认知分析结果
Query: [User's question]
查询内容:[用户问题]
Layer 1: Language Mechanics
层级1:语言机制
[L1 agent result]
[L1代理结果]
Layer 2: Design Choices
层级2:设计选型
[L2 agent result]
[L2代理结果]
Layer 3: Domain Constraints
层级3:领域约束
[L3 agent result]
[L3代理结果]
Cross-Layer Synthesis
跨层综合分析
Reasoning Chain
推理链
L3 Domain: [Constraint]
↓ implies
L2 Design: [Pattern]
↓ implemented via
L1 Mechanism: [Feature]L3 领域:[约束条件]
↓ 推导得出
L2 设计:[模式]
↓ 通过以下方式实现
L1 机制:[特性]Final Recommendation
最终推荐
Do: [Recommended approach]
Don't: [What to avoid]
Code Pattern:
rust
// Recommended implementationAnalysis performed by meta-cognition-parallel v0.1.0 (experimental)
undefined建议: [推荐方案]
避免: [需要规避的做法]
代码示例:
rust
// 推荐实现方式分析由 meta-cognition-parallel v0.1.0(实验性)执行
undefinedTest Scenarios
测试场景
Test 1: Trading System E0382
测试1:交易系统E0382错误
/meta-parallel 交易系统报 E0382,trade record 被 move 了Expected: L3 identifies FinTech constraints → L2 suggests shared immutable → L1 recommends Arc<T>
/meta-parallel 交易系统报 E0382,trade record 被 move 了预期结果:L3识别出金融科技领域约束 → L2建议使用不可变共享模式 → L1推荐使用Arc<T>
Test 2: Web API Concurrency
测试2:Web API并发问题
/meta-parallel Web API 中多个 handler 需要共享数据库连接池Expected: L3 identifies Web constraints → L2 suggests connection pooling → L1 recommends Arc<Pool>
/meta-parallel Web API 中多个 handler 需要共享数据库连接池预期结果:L3识别出Web领域约束 → L2建议使用连接池模式 → L1推荐使用Arc<Pool>
Test 3: CLI Tool Config
测试3:CLI工具配置处理
/meta-parallel CLI 工具如何处理配置文件和命令行参数的优先级Expected: L3 identifies CLI constraints → L2 suggests config precedence pattern → L1 recommends builder pattern
/meta-parallel CLI 工具如何处理配置文件和命令行参数的优先级预期结果:L3识别出CLI领域约束 → L2建议使用配置优先级模式 → L1推荐使用构建器模式
Limitations (Experimental)
局限性(实验性)
- Subagent results are summarized, may lose detail
- Parallel execution depends on Claude Code version
- Cross-layer synthesis quality depends on result structure
- May have higher latency than sequential approach
- 子代理结果会被摘要处理,可能丢失细节
- 并行执行依赖Claude Code版本
- 跨层综合分析的质量取决于结果的结构化程度
- 延迟可能高于顺序分析方案
Feedback
反馈
This is experimental. Please report issues and suggestions to improve the three-layer parallel analysis approach.
本功能为实验性版本。请反馈问题和建议,以改进三层并行分析方案。