gstack/diagnose
Milan 09ddb4a38e fix: diagnose anti-convergence guardrails — environment check, workflow map, narrative bias
Analyzed a real diagnostic session that wasted 500+ lines querying the wrong
database, skipped the workflow map, jumped between hypotheses without testing,
and declared confidence 8/10 without reproducing the issue.

New guardrails:
- "5 Deadly Sins" section: wrong database, skipping workflow map, narrative
  bias, premature confidence, sequential hypothesis testing
- Phase 0-env: mandatory environment verification before ANY database query
  (print host/db, verify it matches the reported environment)
- Phase 1f: "MANDATORY BEFORE ANY HYPOTHESIS" with explicit warning about
  the #1 failure mode (skipping the map → anchoring on first suspicious thing)
- Evidence Gate 1: now a printable checklist that must include workflow map
  completion; "print it with answers" instruction
- Anti-narrative rule in Phase 2: catch "so it must be..." reasoning
- Anti-premature-convergence rules: max confidence 7 without reproduction,
  "what ELSE could explain this?" prompt after every suspicious finding

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-04-08 19:27:22 -07:00
..
SKILL.md fix: diagnose anti-convergence guardrails — environment check, workflow map, narrative bias 2026-04-08 19:27:22 -07:00
SKILL.md.tmpl fix: diagnose anti-convergence guardrails — environment check, workflow map, narrative bias 2026-04-08 19:27:22 -07:00