{"kind":"Skill","metadata":{"namespace":"community","name":"thinking-dual-process","version":"0.1.0"},"spec":{"description":"Apply Kahneman's Dual-Process Theory to recognize when to trust intuition vs engage deliberate analysis. Use for high-stakes decisions, error-prone contexts, or when balancing speed vs accuracy.","files":{"SKILL.md":"---\nname: thinking-dual-process\ndescription: Apply Kahneman's Dual-Process Theory to recognize when to trust intuition vs engage deliberate analysis. Use for high-stakes decisions, error-prone contexts, or when balancing speed vs accuracy.\n---\n\n# Dual-Process Thinking\n\n## Overview\nBased on Daniel Kahneman's research (popularized in \"Thinking, Fast and Slow\"), Dual-Process Theory describes two distinct modes of thought: System 1 (fast, intuitive, automatic) and System 2 (slow, deliberate, analytical). Understanding when each system is active—and when each is appropriate—helps you avoid cognitive errors and make better decisions.\n\n**Core Principle:** Know which system is driving your thinking. Engage System 2 for high-stakes decisions; trust System 1 for routine tasks and expert domains.\n\n## When to Use\n- Making decisions with significant consequences\n- Recognizing when intuition may mislead\n- Balancing speed vs accuracy tradeoffs\n- Reviewing work for cognitive errors\n- Teaching or coaching decision-making\n- When \"something feels off\" but you can't articulate why\n- Before trusting a gut feeling on important matters\n\nDecision flow:\n```\nMaking a decision? → High stakes? → yes → Unfamiliar domain? → yes → ENGAGE SYSTEM 2\n                                   ↘ no → System 1 may suffice\n                  ↘ no → Time pressure? → yes → System 1 appropriate\n                                        ↘ no → Choose based on complexity\n```\n\n## The Two Systems\n\n### System 1: Fast Thinking\n| Characteristic | Description |\n|----------------|-------------|\n| **Speed** | Instant, automatic |\n| **Effort** | Effortless, no strain |\n| **Control** | Involuntary, always on |\n| **Mode** | Intuitive, associative |\n| **Emotion** | Emotionally charged |\n| **Basis** | Pattern recognition, heuristics |\n\nSystem 1 excels at:\n- Recognizing faces and emotions\n- Detecting hostility in a voice\n- Reading text effortlessly\n- Driving on an empty road\n- Finding 2 + 2\n- Expert pattern recognition (chess masters, experienced doctors)\n\nSystem 1 fails at:\n- Complex calculations (17 × 24)\n- Logical analysis of arguments\n- Statistical reasoning\n- Resisting cognitive biases\n- Novel, unfamiliar problems\n\n### System 2: Slow Thinking\n| Characteristic | Description |\n|----------------|-------------|\n| **Speed** | Slow, sequential |\n| **Effort** | Effortful, depleting |\n| **Control** | Deliberate, voluntary |\n| **Mode** | Analytical, rule-following |\n| **Emotion** | Can override emotions |\n| **Basis** | Logic, computation, rules |\n\nSystem 2 excels at:\n- Complex computations\n- Logical reasoning\n- Comparing options systematically\n- Following explicit rules\n- Self-monitoring and correction\n- Novel problem-solving\n\nSystem 2 fails at:\n- Sustaining attention (gets tired)\n- Operating under time pressure\n- Processing when cognitively depleted\n- Noticing when it should activate\n\n## The Process\n\n### Step 1: Identify Active System\nWhich system is currently driving your thinking?\n\nSystem 1 indicators:\n- Answer came immediately\n- Feels obvious or intuitive\n- High confidence without analysis\n- Emotional reaction present\n- \"I just know\"\n\nSystem 2 indicators:\n- Had to concentrate\n- Worked through steps explicitly\n- Mental effort required\n- Considered alternatives\n- \"Let me think about this\"\n\n```\nExample: \"Should we approve this vendor contract?\"\nGut says \"yes\" immediately → System 1 active\nPause: Is this appropriate for this decision?\n```\n\n### Step 2: Assess Appropriateness\nIs the active system appropriate for this context?\n\n**Trust System 1 when:**\n- Domain is familiar with clear feedback loops\n- You have extensive relevant experience\n- Patterns are valid and stable\n- Decision is reversible\n- Speed matters more than precision\n- Cost of error is low\n\n**Engage System 2 when:**\n- Domain is unfamiliar or complex\n- Stakes are high\n- Statistical reasoning required\n- System 1 biases likely apply\n- Decision is irreversible\n- You feel very confident (check for overconfidence)\n- \"Obvious\" answer benefits you (check for motivated reasoning)\n\n### Step 3: Override if Needed\nIf System 1 is active but System 2 is appropriate:\n\n```\n1. PAUSE - Interrupt automatic response\n2. ARTICULATE - State the decision explicitly\n3. ANALYZE - Apply structured thinking\n4. CHECK - Look for bias indicators\n5. DECIDE - Make deliberate choice\n```\n\nOverride triggers (red flags):\n- High emotional charge\n- Time pressure being used tactically\n- \"Everyone agrees\" (groupthink)\n- Round numbers without analysis\n- First option presented\n- Confirmation of existing beliefs\n\n### Step 4: Execute Appropriately\nMatch your process to the system:\n\n| System | Process |\n|--------|---------|\n| System 1 (validated) | Trust intuition, act quickly, monitor outcomes |\n| System 2 (engaged) | Use checklists, seek outside view, document reasoning |\n\n## System 1 Failure Modes\n\n### Substitution\nSystem 1 replaces hard questions with easier ones:\n```\nHard: \"How much should I pay for this stock?\"\nSubstituted: \"How much do I like this company?\"\n\nHard: \"Is this candidate qualified?\"  \nSubstituted: \"Does this candidate seem likeable?\"\n```\n\n### Heuristic Errors\n\n| Heuristic | What It Does | When It Fails |\n|-----------|--------------|---------------|\n| Availability | Judges by ease of recall | Vivid events seem more common |\n| Representativeness | Matches to stereotypes | Ignores base rates |\n| Anchoring | Starts from given number | Arbitrary anchors still influence |\n| Affect | Decides by feeling | Emotions override data |\n| Confirmation | Seeks supporting evidence | Misses contradicting evidence |\n\n### WYSIATI (What You See Is All There Is)\nSystem 1 builds the best story from available information:\n```\nGiven: \"John is tall and muscular\"\nSystem 1 concludes: \"John is probably athletic\"\nMissing: John's actual athletic ability, base rates, context\n```\n\nSystem 1 doesn't flag missing information—it works with what's available.\n\n## Cognitive Ease vs Strain\n\n### Cognitive Ease (System 1 Active)\nFeels: Familiar, true, good, effortless\nRisks: \n- Reduced vigilance\n- Accepting false statements\n- Overconfidence\n- Missing errors\n\nInduced by:\n- Repeated exposure\n- Clear display\n- Primed ideas\n- Good mood\n\n### Cognitive Strain (System 2 Engaged)\nFeels: Unfamiliar, requiring effort, suspicious\nBenefits:\n- Increased vigilance\n- More analytical processing\n- Reduced biases\n- Better accuracy\n\nInduced by:\n- Poor print quality\n- Complex language\n- Novel situations\n- Bad mood\n\n**Tactical tip:** For important decisions, deliberately induce mild cognitive strain (different format, pause before answering) to engage System 2.\n\n## Application Examples\n\n### Code Review\n```\nSystem 1 mode: \"This looks fine\" (pattern matches familiar code)\nEngage System 2: \n- Is this a high-risk change?\n- Am I the right reviewer for this domain?\n- Have I actually traced the logic?\n- What edge cases might I miss?\n```\n\n### Hiring Decisions\n```\nSystem 1 mode: \"Great interview, strong hire\" (likeability heuristic)\nEngage System 2:\n- Structured scorecard vs overall impression\n- Compare to job requirements, not to other candidates\n- Check for halo effect from one strong answer\n- Seek disconfirming information\n```\n\n### Architecture Decisions\n```\nSystem 1 mode: \"Let's use [familiar technology]\" (availability)\nEngage System 2:\n- Explicit requirements analysis\n- Evaluate alternatives against criteria\n- Consider long-term implications\n- Document reasoning\n```\n\n### Debugging\n```\nSystem 1 mode: \"It's probably X\" (first hypothesis feels right)\nEngage System 2:\n- List all possible causes\n- Assign probabilities (Bayesian)\n- Test systematically, not just hunches\n- Consider unlikely explanations\n```\n\n## Integration with Other Thinking Skills\n\n### With Debiasing\nSystem 1 is the source of most cognitive biases. The debiasing checklist is essentially a System 2 override protocol:\n```\nAutomatic response → Pause → Apply debiasing checklist → Override if needed\n```\n\n### With Bayesian Reasoning\nSystem 1 ignores base rates; System 2 applies them:\n```\nSystem 1: \"Positive test result = probably have condition\"\nSystem 2: Apply Bayes' Theorem with actual base rates\n```\n\n### With First Principles\nSystem 1 reasons by analogy; System 2 enables first principles:\n```\nSystem 1: \"Competitors do X, so we should too\"\nSystem 2: \"What are the fundamental requirements? Build from there\"\n```\n\n### With Pre-Mortem\nSystem 1 is optimistic; pre-mortem forces System 2 pessimism:\n```\nSystem 1: \"This plan will work\" (overconfidence)\nSystem 2: \"Imagine it failed. Why?\" (deliberate analysis)\n```\n\n### With OODA Loop\nBalance speed (System 1) with accuracy (System 2) based on context:\n```\nIncident response: System 1 pattern matching for speed\nPost-incident: System 2 analysis for root cause\n```\n\n## Expert Intuition: When System 1 Is Valid\n\nNot all intuition is suspect. Expert intuition can be trusted when:\n\n1. **High-validity environment**: Clear patterns exist\n2. **Extensive practice**: Thousands of hours of deliberate practice  \n3. **Rapid feedback**: Immediate correction signals\n4. **Stable patterns**: Domain rules don't change frequently\n\n```\nValid expert intuition:\n- Chess grandmasters recognizing positions\n- Firefighters sensing danger\n- Experienced nurses detecting deterioration\n\nSuspect expert intuition:\n- Stock pickers predicting markets\n- Political pundits forecasting elections\n- Interviewers predicting job performance\n```\n\nAsk: \"Has this person had opportunities to learn the valid patterns through repeated, well-calibrated feedback?\"\n\n## Verification Checklist\n- [ ] Identified which system is currently active\n- [ ] Assessed if active system is appropriate for stakes/context\n- [ ] Checked for cognitive ease that might mask errors\n- [ ] Applied System 2 override if high-stakes or unfamiliar\n- [ ] Used structured process for System 2 decisions\n- [ ] Documented reasoning for important decisions\n- [ ] Considered base rates and statistics, not just intuition\n\n## Key Questions\n- \"Did this answer come too easily?\"\n- \"Am I in a domain where my intuition is calibrated?\"\n- \"What would System 2 analysis reveal?\"\n- \"Is my confidence justified by analysis or just feeling?\"\n- \"What information am I not seeing (WYSIATI)?\"\n- \"Would I decide the same way if I had to defend the reasoning?\"\n\n## Kahneman's Warning\n\"The confidence people have in their beliefs is not a measure of the quality of evidence but of the coherence of the story the mind has managed to construct.\"\n\nSystem 1 builds compelling stories from limited information and feels very confident doing so. That confidence is often unwarranted. Engage System 2 when the stakes matter.\n"},"import":{"commit_sha":"a31e22d4445ad8fef7cd771d32af537aebb68c49","imported_at":"2026-05-22T21:14:39Z","license_text":"MIT License\n\nCopyright (c) 2025 TJ Boudreaux\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.\n","owner":"tjboudreaux","repo":"tjboudreaux/cc-thinking-skills","source_url":"https://github.com/tjboudreaux/cc-thinking-skills/tree/a31e22d4445ad8fef7cd771d32af537aebb68c49/skills/thinking-dual-process"}},"content_hash":[165,18,87,154,62,145,13,210,8,10,200,42,212,100,66,42,139,184,177,160,24,122,250,182,151,162,178,238,71,165,200,223],"trust_level":"unsigned","yanked":false}