skills.rest
park-kyungchan
park-kyungchanCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Enforce a four-phase debugging process requiring root-cause investigation before fixes.

Updated Aug 23, 2026
Search Tags:#debugging#root cause#defense-in-depth#reproducibility#phase-based#trace-back#hypothesis-testing
One-click install
npx skills add https://github.com/park-kyungchan/palantir --skill systematic-debugging-park-kyungchan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/park-kyungchan/palantir/tree/main/.claude/plugins/cache/claude-plugins-official/superpowers/4.2.0/skills/systematic-debugging
Command: npx skills add https://github.com/park-kyungchan/palantir --skill systematic-debugging-park-kyungchan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined approach to debugging by insisting on root-cause investigation before fixes, preventing symptom-focused patches and promoting reliable, faster resolution over time.

Core Features & Use Cases

  • Phase-based framework: Phase 1 Root Cause Investigation, Phase 2 Pattern Analysis, Phase 3 Hypothesis and Testing, Phase 4 Implementation.
  • Anti-patterns and red flags to avoid shortcuts under pressure.
  • Guidance on tracing data flow, enabling defense-in-depth, and stack-trace instrumentation.
  • Applicable to any technical issue: bugs, test failures, performance problems, and integration issues.

Quick Start

  1. Read the overview and the four phases; then begin Phase 1 root-cause investigation before proposing fixes.
  2. Identify evidence, reproduce consistently, and document findings to support a root-cause hypothesis.
  3. Only after Phase 1 is complete should you propose fixes and implement Phase 4 once validated.

Frequently Asked Questions about systematic-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to find the root cause of a software bug instead of just patching symptoms?▼

Systematic debugging enforces a root-cause investigation phase before applying fixes, ensuring you trace data flow and reproduce consistently to prevent symptom-focused patches. This approach promotes reliable resolution over time.

How do I debug test failures and performance problems using a phase-based approach?▼

Debug test failures and performance problems through a four-phase workflow: investigate root causes, analyze patterns, test hypotheses, and implement validated fixes. This prevents shortcuts under pressure and ensures reliable resolution.

How can I consistently reproduce technical issues to support a root-cause hypothesis?▼

Consistently reproduce technical issues by gathering evidence and documenting findings during the initial investigation phase. This documented evidence directly supports forming an accurate root-cause hypothesis before proceeding to pattern analysis.

When should I stop debugging and what are the red flags indicating I am taking shortcuts?▼

Stop debugging when explicit stop conditions are met and a root cause cannot be found. Red flags include skipping the investigation phase, patching symptoms under pressure, and avoiding stack-trace instrumentation or defense-in-depth analysis.

Does this systematic debugging approach work for environment-related failures and integration issues?▼

Yes, this systematic debugging approach applies to environment-related failures, integration issues, bugs, and test failures across software systems. It enforces hypothesis testing and pattern analysis regardless of the technical issue type.

Why does root cause investigation need to happen before proposing fixes for a bug?▼

Root cause investigation must happen before proposing fixes to prevent symptom-focused patches. Enforcing this initial phase ensures you trace data flow and validate hypotheses, leading to reliable and faster resolution over time.

Related Skills

Explore More Software Engineering Skills→
cryptopaficryptopafi

systematic-debugging

Diagnose and document root causes through a four-phase investigation workflow.

Community
Advanced
trungdo9trungdo9
3

debugging

Guide systematic software debugging with root cause tracing and validation.

Community
Advanced
dige04dige04

Debugging

Guide root-cause debugging through a four-phase investigation and verification process.

Community
Advanced
lv7devlv7dev

debugging

Investigate root causes before implementing fixes through a four-phase debugging workflow.

Community
Advanced