Cognitive Biases Awareness

---
name: cognitive-biases-awareness
description: "Use when identifying cognitive biases."
version: 1.0.0
author: Hermes Agent
license: MIT
platforms: [linux, macos, windows]
metadata:
  hermes:
    tags: ['c', 'o', 'g', 'n', 'i', 't', 'i', 'v', 'e', '-', 'b', 'i', 'a', 's', 'e', 's', ',', ' ', 'p', 's', 'y', 'c', 'h', 'o', 'l', 'o', 'g', 'y']
    related_skills: [general]
---

## Overview
Cognitive Biases Awareness implementation. Covers essential methodologies, 
best practices, technical foundations, and verification approaches for this domain.

## When to Use
- "Cognitive Biases Awareness implementation"
- "Best practices for Cognitive Biases Awareness"
- "Cognitive Biases Awareness optimization and enhancement"
- "Cognitive Biases Awareness troubleshooting"
- "Cognitive Biases Awareness performance and cost analysis"

## Key Methodologies
1. Assessment and Planning Phase
2. Implementation and Execution  
3. Monitoring and Optimization
4. Compliance and Verification
5. Continuous Improvement

## Common Pitfalls
1. **Insufficient planning** — rushing without proper assessment
2. **Ignoring industry standards** — not following best practices
3. **Poor stakeholder alignment** — conflicting requirements
4. **Inadequate measurement** — no metrics to track success
5. **Not accounting for context** — generic approaches fail
6. **Underestimating complexity** — oversimplified solutions
7. **No contingency planning** — unhandled failure scenarios
8. **Insufficient validation** — implementation without testing
9. **Not documenting decisions** — lost knowledge and context
10. **Failing to iterate** — not improving based on feedback

## Verification Checklist
- [ ] Initial assessment and requirements gathering completed
- [ ] Industry standards and best practices reviewed
- [ ] Design validated with stakeholders
- [ ] Implementation plan with milestones defined
- [ ] Quality control and validation approaches
- [ ] Testing and verification procedures established
- [ ] Monitoring and feedback mechanisms
- [ ] Documentation complete and accessible
- [ ] Training provided to relevant stakeholders
- [ ] Post-implementation review and improvement plan