plugins/kronen/skills/hypothesis-generator/SKILL.md
Generate three competing hypotheses for a debugging problem, then investigate each in parallel and synthesize evidence to identify the root cause. Extends root-cause-debugging with structured hypothesis management. Use when a bug's root cause is unclear after initial evidence gathering, when a previous fix failed and the cause is still unknown, when multiple subsystems could plausibly be at fault, or when confirmation bias in investigation needs to be avoided.
npx skillsauth add hjemmesidekongen/ai hypothesis-generatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate three competing hypotheses, investigate each, synthesize — then fix. Eliminates confirmation bias by forcing investigation of alternative causes.
After Phase 1 of root-cause-debugging when evidence doesn't clearly point to one cause. Do NOT use for obvious bugs — only when genuinely uncertain.
After evidence gathering:
Hypothesis A: most obvious explanation
Hypothesis B: different mechanism, same symptom
Hypothesis C: deeper/systemic cause (the non-obvious one)
Each needs: Cause | Mechanism | Prediction | Test
Investigate all three (parallel if possible)
Score each: CONFIRMED / POSSIBLE / REFUTED
Synthesize → select confirmed hypothesis → enter Phase 4
One confirmed → Phase 3 hypothesis. Two confirmed → find unifying root cause. All refuted → return to Phase 1. All possible → run most discriminating test.
Full process: root-cause-debugging/references/process.md — Hypothesis-Driven Extension.
development
Creates a brand from scratch through market research and interactive sparring. Runs competitive research via Perplexity, then guides the user through positioning, audience, voice, values, and content pillars. Produces the full brand guideline set at .ai/brand/{name}/. Use when building a new brand, defining brand strategy for a product, or when /våbenskjold:create is invoked.
testing
Loads brand guidelines from .ai/brand/{name}/ and makes them available to the current context. Progressive disclosure: L1 confirms brand exists, L2 loads summary, L3 loads specific files on demand. Use when a downstream skill or user needs brand context, or when /våbenskjold:apply is invoked.
documentation
Guided reinvention of an existing brand guideline. Loads current brand from .ai/brand/{name}/, identifies what to keep vs change, and walks the user through targeted evolution. Preserves brand equity while updating positioning, voice, or values. Use when refreshing a brand or when /våbenskjold:evolve is invoked.
development
Codifies an existing brand from materials, samples, and references. Analyzes provided content to extract voice patterns, values, and positioning. Produces the same guideline format as brand-strategy. Use when a brand already exists but isn't documented, or when /våbenskjold:audit is invoked.