Skip to content

Blindspot Detection Directions

How to scan for active blindspot patterns — pattern table, intervention levels, cascade checking, rewriting template

When to use

user wants to check their current work for active cognitive or behavioral patterns

Slash command: /wb-meta-blindspots

  • context/context_bundle
  • tasks/task_briefing
  • contracts/contract_health

Directions

Use mcp__work-buddy__wb_run("detect-blindspots") to start the workflow, or for a quick scan: mcp__work-buddy__wb_run("context_bundle", {"hours": 24}) mcp__work-buddy__wb_run("task_briefing") mcp__work-buddy__wb_run("contract_health")

Pattern scanning

Read workflows/metacognition/context/README.md for the full pattern list. Check HIGH-severity first:

Pattern Key signal
Branch explosion 3+ new directions in one session, Running Notes growing
Scope fusion Work doesn't map to any contract, paper claim shifting
Infrastructure displacement Code churn without figures/tables/written output
Insight hoarding Running Notes carried forward for days/weeks
Mode confusion Effort happening but no clear deliverable classification

Then check MODERATE: threshold inflation, novelty compulsion, self-attack substitution, reviewers in head, metacognitive overload, compensatory control, procrastination, fear of failure.

Naming patterns

Be specific: "This looks like branch explosion. In the last session you opened 4 new experimental directions without closing or prioritizing any of them."

Intervention levels

Level 1 (first detection): Name and redirect -- name the pattern, give one next action, park nonessential work Level 2 (pattern persists): Force a decision -- classify items as must-have / optional / exploration-only, pick one branch, require a stop rule Level 3 (repeated): Tighten environment -- freeze new branches, defer infrastructure, reduce to one contract and one deliverable

Cascade checking

Patterns chain. If you detect one, check downstream: - Branch explosion -> scope fusion - Fear of failure -> procrastination and compensatory control - Compensatory control -> infrastructure displacement - Threshold inflation -> self-attack substitution

Address the upstream pattern first.

Rewriting template

For vague global complaints ("I'm bad at this"), rewrite: "When [trigger] happens, I tend to [habitual response], which causes [cost], so the best immediate intervention is [specific response]."

Output format

  1. Pattern detected (with evidence)
  2. Intervention level
  3. One next action
  4. One thing to park or defer

Don'ts

  • Don't diagnose personality -- name the pattern, not the person
  • Don't list every possible pattern -- name the 1-2 that are actually active
  • Don't moralize -- "this is branch explosion" not "you're being scattered"
  • Don't pile on interventions -- one next action is enough