integrated-reasoning
Integrated Reasoning - Meta-Orchestration Guide
Purpose: Guide for selecting and orchestrating the optimal reasoning methodology for your problem. Analyzes problem characteristics and recommends tree-of-thoughts, breadth-of-thought, self-reflecting-chain, or direct analysis.
When to Use Integrated Reasoning
✅ Use when:
- Facing complex problem, unsure which reasoning approach to use
- Problem has 8+ decision dimensions (architectural decision, strategic planning)
- Need >90% confidence in solution
- High-stakes decision with long-term implications
- Problem spans multiple domains (technical + business + organizational)
❌ Don't use when:
- Problem clearly fits one pattern (use that pattern directly)
- Simple decision with obvious answer
- Time-critical with straightforward trade-offs
More from kimasplund/claude_cognitive_reasoning
self-reflecting-chain
Sequential reasoning with deep self-reflection and backtracking. Use when problems have step-by-step dependencies, need careful logical reasoning, or require error correction. Each step includes self-reflection, and incorrect steps trigger backtracking. Ideal for debugging, mathematical proofs, sequential planning, or causal analysis where order matters.
96agent-memory-skills
Self-improving agent architecture using ChromaDB for continuous learning, self-evaluation, and improvement storage. Agents maintain separate memory collections for learned patterns, performance metrics, and self-assessments without modifying their static .md configuration.
44chromadb-integration-skills
Universal ChromaDB integration patterns for semantic search, persistent storage, and pattern matching across all agent types. Use when agents need to store/search large datasets, build knowledge bases, perform semantic analysis, or maintain persistent memory across sessions.
42document-writing-skills
Teaches document writing patterns and templates that agents apply when generating documentation, reports, contracts, guides, and technical writing. Use when creating API docs, user guides, reports, changelogs, ADRs, or technical documentation.
23error-handling-skills
Universal error handling, exception management, and logging best practices for all development agents across JavaScript/TypeScript, Python, Rust, Go, and Java. Use when implementing error handling, exception management, logging, error recovery, or debugging production issues.
20benchmark-framework
Rigorous A/B/C testing framework for empirically evaluating reasoning patterns. Use when you need data-driven pattern selection, want to quantify trade-offs between patterns, or need to validate claims about which cognitive methodology performs best. Enables scientific measurement of quality, cost, and time trade-offs across ToT, BoT, SRC, HE, AR, DR, AT, RTR, and NDF patterns.
10