plugins/kronen/skills/root-cause-debugging/SKILL.md
4-phase mandatory investigation protocol before any fix is attempted: Investigate → Pattern Analysis → Hypothesis → Implement. Prevents band-aid fixes by requiring evidence gathering, pattern identification, and a testable hypothesis before touching code. Includes escalation tree, anti-patterns (shotgun debugging, fix-and-pray, symptom fixation), symptom-to-tool mapping, and framework-aware debugging references. If 3+ fixes fail, escalate to architecture review. Use when diagnosing a bug or unexpected behavior, when a quick fix isn't working and the problem keeps returning, when a test is failing and the cause isn't immediately obvious, when a system behaves differently than expected, or when debugging any framework-specific issue (load the relevant tech skill's references/debugging.md for framework detail).
npx skillsauth add hjemmesidekongen/ai root-cause-debuggingInstall 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.
No fix before understanding. Symptoms are not root causes.
Phase 1: INVESTIGATE — gather all evidence before forming opinions
Phase 2: PATTERN — find what the evidence has in common
Phase 3: HYPOTHESIS — state a specific, testable cause + prediction
Phase 4: IMPLEMENT — fix the root cause, verify with verification-gate
If 3 or more fixes fail to resolve the problem: stop. The architecture may be wrong. Surface the pattern to the user before attempting more fixes.
See references/process.md for the full investigation methodology,
root-cause tracing technique, defense-in-depth layers, and
condition-based waiting pattern.
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.