se-debug

Trace causal chains from trigger to symptom to confirm root causes.

Updated May 7, 2026
One-click install
npx skills add https://github.com/simonwjackson/pi-software-engineering --skill se-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: se-debug
Source: https://github.com/simonwjackson/pi-software-engineering/tree/main/skills/se-debug
Command: npx skills add https://github.com/simonwjackson/pi-software-engineering --skill se-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers diagnose bugs by tracing the full causal chain from trigger to symptom, ensuring fixes address the root cause rather than symptoms.

Core Features & Use Cases

  • Phase-driven debugging workflow that guides triage, investigation, root-cause analysis, and optional fixes.
  • Structured reasoning to identify and document the causal chain with evidence and hypotheses.
  • Test-first approach that validates fixes and prevents regression, with clear handoff documentation for deployment.

Quick Start

Describe the bug, trace to the root cause, and implement a minimal, test-first fix.

Frequently Asked Questions about se-debug

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

FAQPage Schema
How do I debug software to find the root cause instead of just fixing symptoms?

Root-cause debugging requires tracing the full causal chain from trigger to symptom before proposing changes. This structured approach enforces confirming the actual origin through evidence and hypotheses instead of patching superficial symptoms.

What is the best way to structure a debugging workflow for complex bugs across multiple components?

A phase-based debugging workflow systematically guides engineers through triage, investigation, root-cause analysis, and optional fixes. This structured process manages complex bugs across multiple components by enforcing evidence and hypothesis tracking.

How do I prevent regressions when implementing a bug fix?

Prevent regressions during bug fixes by enforcing a test-first approach that validates changes before deployment. Documenting the causal chain and handoff details ensures the fix is verified and prevents future symptom regressions.

Can I use a test-first approach to validate fixes during root-cause analysis?

Yes, applying a test-first approach validates minimal fixes during root-cause analysis. This confirms the identified causal chain is resolved and prevents regressions by enforcing test validation before any code changes are finalized.

When should I not use a phase-based debugging workflow?

Avoid using a phase-based debugging workflow for simple, isolated bugs where the root cause is immediately obvious. This structured troubleshooting process is designed for complex issues across multiple components requiring triage and deep investigation.