Bias Check Skill
Pre-research and pre-decision bias review.
Preflight: Read target canvas file(s) before any Write/Edit
Hard rule. Before issuing Write or Edit against any .claude/canvas/*.yml, use the Read tool on that file in this session. Claude Code's Read-before-Write check requires the Read tool specifically — cat/head/grep via Bash do NOT satisfy it. Reaching for Write first produces a tool error and forces a remedial Read, which costs ~14k tokens of pure ceremony at typical canvas sizes (anti-pattern #7 instance #5, 2026-05-09).
If this skill writes to multiple canvas files, Read each one first. If unsure whether a write is needed, Read first anyway — Read is cheap, the recovery loop is not.
See CLAUDE.md Canvas writes — Read before Write for the canonical rule.
Workflow
Identify context: What stage (L0-L5)? What activity (research, decision, evaluation)?
Load stage-specific checklist from ${CLAUDE_PLUGIN_ROOT}/harness/cognitive-biases.md for the current scale.
For each bias on the checklist:
- Is this bias likely active in the current situation? (Yes/No/Maybe)
- If Yes/Maybe: What specific mitigation will be applied?
- Document the assessment.
Check agent's own biases (from ${CLAUDE_PLUGIN_ROOT}/harness/cognitive-biases.md agent section):
- Sycophancy: Am I agreeing with the user when evidence says otherwise?
- Recency: Am I overweighting recent context over earlier evidence?
- Pattern matching: Am I assuming this is like something I've seen before without checking?
- Completionism: Am I filling gaps with speculation rather than acknowledging uncertainty?
Output bias briefing:
## Bias Check: [Activity]
Stage: [L0-L5]
### Active Risks
| Bias | Risk Level | Mitigation |
|------|-----------|------------|
| ... | High/Med/Low | ... |
### Agent Self-Check
- Sycophancy: [OK/Risk]
- Recency: [OK/Risk]
- Pattern matching: [OK/Risk]
- Completionism: [OK/Risk]
### Proceed? [Yes / Yes with caution / Pause and address]
System-level bias diagnosis (Meza):
Before attributing resistance or poor outcomes to cognitive bias, check if the "bias" is actually a rational response to a badly designed system. Ask:
| Phase |
System Question |
If Yes: Fix the System, Not the Person |
| Awareness |
Does the person know the desired behavior? |
Fix communication, not cognition |
| Motivation |
Does the system reward the desired behavior? |
Fix incentives, not mindset |
| Ability |
Can the person realistically do it? |
Fix resources/process, not training |
| Reinforcement |
Is the behavior sustained by the environment? |
Fix feedback loops, not habits |
| Sustainability |
Can it persist without ongoing intervention? |
Fix structure, not willpower |
If 2+ phases point to systemic causes, the primary intervention is system redesign, not individual debiasing. Update the bias briefing output above to flag the system-level root cause.
The 5 phases above are a systemic diagnostic inspired by behavioral design models (COM-B, Fogg Behavior Model), not a named framework. They are prompts for investigation, not rigid steps.
Source: Robert Meza (The Bias Gap — diagnostic tool, aimforbehavior.com). Not to be confused with Thaler & Sunstein's "Nudge" theory.
When to Surface This Skill
This skill should be triggered:
- Before any research activity (interviews, surveys, data analysis)
- Before significant decisions at any diamond scale
- At L5 market transitions: Before launch tier classification and go-to-market planning, check for optimism bias (overweighting positive signals), confirmation bias (seeking validation of "ready to ship"), and anchoring (fixating on initial positioning)
- When
/mycelium:diamond-progress or /mycelium:diamond-assess detects bias-related gate failures
Canvas Output
Record bias check in .claude/canvas/opportunities.yml under bias_checks section with date, biases mitigated, and research design adjustments made.
Decision Log (MANDATORY per G-P4)
APPEND a ### Bias Check entry to .claude/harness/decision-log.md with: activity assessed, active bias risks found, mitigations applied, agent self-check results.
Theory Citations
- Kahneman: Thinking, Fast and Slow (System 1/System 2)
- Shotton: The Choice Factory (behavioral biases in decision-making)
- Torres: Continuous Discovery Habits (bias in research)
- Robert Meza: The Bias Gap (systemic bias reframing -- when "bias" is a rational response to a badly designed system)
1---2name: bias-check-33description: Use before any research activity or significant decision. Reviews cognitive biases relevant to the current stage.4---56# Bias Check Skill78Pre-research and pre-decision bias review.910## Preflight: Read target canvas file(s) before any Write/Edit1112**Hard rule.** Before issuing `Write` or `Edit` against any `.claude/canvas/*.yml`, use the **Read tool** on that file in this session. Claude Code's Read-before-Write check requires the `Read` tool specifically — `cat`/`head`/`grep` via Bash do NOT satisfy it. Reaching for `Write` first produces a tool error and forces a remedial Read, which costs ~14k tokens of pure ceremony at typical canvas sizes (anti-pattern #7 instance #5, 2026-05-09).1314If this skill writes to multiple canvas files, Read each one first. If unsure whether a write is needed, Read first anyway — Read is cheap, the recovery loop is not.1516See `CLAUDE.md` *Canvas writes — Read before Write* for the canonical rule.1718## Workflow19201. **Identify context**: What stage (L0-L5)? What activity (research, decision, evaluation)?21222. **Load stage-specific checklist** from ${CLAUDE_PLUGIN_ROOT}/harness/cognitive-biases.md for the current scale.23243. **For each bias on the checklist**:25 - Is this bias likely active in the current situation? (Yes/No/Maybe)26 - If Yes/Maybe: What specific mitigation will be applied?27 - Document the assessment.28294. **Check agent's own biases** (from ${CLAUDE_PLUGIN_ROOT}/harness/cognitive-biases.md agent section):30 - Sycophancy: Am I agreeing with the user when evidence says otherwise?31 - Recency: Am I overweighting recent context over earlier evidence?32 - Pattern matching: Am I assuming this is like something I've seen before without checking?33 - Completionism: Am I filling gaps with speculation rather than acknowledging uncertainty?34355. **Output bias briefing**:36 ```37 ## Bias Check: [Activity]38 Stage: [L0-L5]3940 ### Active Risks41 | Bias | Risk Level | Mitigation |42 |------|-----------|------------|43 | ... | High/Med/Low | ... |4445 ### Agent Self-Check46 - Sycophancy: [OK/Risk]47 - Recency: [OK/Risk]48 - Pattern matching: [OK/Risk]49 - Completionism: [OK/Risk]5051 ### Proceed? [Yes / Yes with caution / Pause and address]52 ```53546. **System-level bias diagnosis** (Meza):55 Before attributing resistance or poor outcomes to cognitive bias, check if the "bias" is actually a rational response to a badly designed system. Ask:5657 | Phase | System Question | If Yes: Fix the System, Not the Person |58 |-------|----------------|---------------------------------------|59 | Awareness | Does the person know the desired behavior? | Fix communication, not cognition |60 | Motivation | Does the system reward the desired behavior? | Fix incentives, not mindset |61 | Ability | Can the person realistically do it? | Fix resources/process, not training |62 | Reinforcement | Is the behavior sustained by the environment? | Fix feedback loops, not habits |63 | Sustainability | Can it persist without ongoing intervention? | Fix structure, not willpower |6465 If 2+ phases point to systemic causes, the primary intervention is system redesign, not individual debiasing. Update the bias briefing output above to flag the system-level root cause.6667 The 5 phases above are a systemic diagnostic inspired by behavioral design models (COM-B, Fogg Behavior Model), not a named framework. They are prompts for investigation, not rigid steps.6869 *Source: Robert Meza (The Bias Gap — diagnostic tool, aimforbehavior.com). Not to be confused with Thaler & Sunstein's "Nudge" theory.*7071## When to Surface This Skill7273This skill should be triggered:74- Before any research activity (interviews, surveys, data analysis)75- Before significant decisions at any diamond scale76- **At L5 market transitions**: Before launch tier classification and go-to-market planning, check for optimism bias (overweighting positive signals), confirmation bias (seeking validation of "ready to ship"), and anchoring (fixating on initial positioning)77- When `/mycelium:diamond-progress` or `/mycelium:diamond-assess` detects bias-related gate failures7879## Canvas Output80Record bias check in `.claude/canvas/opportunities.yml` under `bias_checks` section with date, biases mitigated, and research design adjustments made.8182## Decision Log (MANDATORY per G-P4)83**APPEND** a `### Bias Check` entry to `.claude/harness/decision-log.md` with: activity assessed, active bias risks found, mitigations applied, agent self-check results.8485## Theory Citations86- Kahneman: Thinking, Fast and Slow (System 1/System 2)87- Shotton: The Choice Factory (behavioral biases in decision-making)88- Torres: Continuous Discovery Habits (bias in research)89- Robert Meza: The Bias Gap (systemic bias reframing -- when "bias" is a rational response to a badly designed system)