EXPERIMENTAL: Three-layer parallel meta-cognition analysis. Triggers on: /meta-parallel, 三层分析, parallel analysis, 并行元认知

Meta Cognition Parallel Analysis (Experimental) Status: Experimental Version: 0.2.0 Last Updated: 2025 01 27 This skill tests parallel three layer cognitive analysis. Concept Instead of sequential analysis, this skill launches three parallel analyzers one for each cognitive layer then synthesizes their results. Usage Example: Execution Mode Detection CRITICAL: Check agent file availability first to determine execution mode. Try to read layer analyzer files: ../../agents/layer1 analyzer.md ../../agents/layer2 analyzer.md ../../agents/layer3 analyzer.md Agent Mode (Plugin Install) Parallel Execution When all layer analyzer files exist at ../../agents/ : Step 1: Parse User Query Extract from $ARGUMENTS : The original question Any code snippets Domain hints (trading, web, embedded, etc.) Step 2: Launch Three Parallel Agents CRITICAL: Launch all three Tasks in a SINGLE message to enable parallel execution. Step 3: Collect Results Wait for all three agents to complete. Each returns structured analysis. Step 4: Cross Layer Synthesis With all three results, perform synthesis per template below. Inline Mode (Skills only Install) Sequential Execution When layer analyzer files are NOT available, execute analysis directly: Step 1: Parse User Query Same as Agent Mode extract question, code, and domain hints from $ARGUMENTS . Step 2: Execute Layer 1 Language Mechanics Analyze the Rust language mechanics involved: Focus areas: Ownership rules (move, copy, borrow) Lifetime annotations Borrowing rules (shared vs mutable) Error codes and their meanings Step 3: Execute Layer 2 Design Choices Analyze the design patterns and trade offs: Focus areas: Smart pointer choices (Box, Rc, Arc) Interior mutability patterns (Cell, RefCell, Mutex) Ownership transfer vs sharing Cloning vs references Step 4: Execute Layer 3 Domain Constraints Analyze domain specific requirements: Focus areas: Industry requirements (FinTech regulations, web scalability, etc.) Performance constraints Safety and correctness requirements Common patterns in the domain Step 5: Cross Layer Synthesis Combine all three layers: Output Template Both modes produce the same output format: L3 Domain: [Constraint] ↓ implies L2 Design: [Pattern] ↓ implemented via L1 Mechanism: [Feature] rust // Recommended implementation Test Scenarios Test 1: Trading System E0382 Expected: L3 identifies FinTech constraints → L2 suggests shared immutable → L1 recommends Arc<T Test 2: Web API Concurrency Expected: L3 identifies Web constraints → L2 suggests connection pooling → L1 recommends Arc<Pool Test 3: CLI Tool Config Expected: L3 identifies CLI constraints → L2 suggests config precedence pattern → L1 recommends builder pattern Error Handling Error Cause Solution Agent files not found Skills only install Use inline mode (sequential) Agent timeout Complex analysis Wait longer or use inline mode Incomplete layer result Agent issue Fill in with inline analysis Limitations Agent Mode: Parallel execution, faster but requires plugin install Inline Mode: Sequential execution, slower but works everywhere Cross layer synthesis quality depends on result structure May have higher latency than simple single layer analysis Feedback This is experimental. Please report issues and suggestions to improve the three layer analysis approach.

meta-cognition-parallel