systematic-debugging

Run systematic debugging sessions for complex technical issue resolution via /investigate command.

1|Updated Jun 22, 2026

Search Tags:#debugging #systematic approach #software development #root-cause analysis #technical troubleshooting

Ready to run

npx skills add https://github.com/jchildree/The-QUESTION --skill systematic-debugging-jchildree

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/jchildree/The-QUESTION/tree/main/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/jchildree/The-QUESTION --skill systematic-debugging-jchildree

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured approach to debugging, root-cause analysis, and architectural decision-making, helping to identify and resolve complex issues efficiently.

Core Features & Use Cases

Investigative Skills: Offers six structured problem-solving workflows for debugging and root-cause analysis.
Investigation Board: Utilizes an Obsidian vault-based shared memory with SPIFFE-inspired attestation for collaborative analysis.
Persona Layer: Implements the DC Comics' Vic Sage voice for a faceless, evidence-driven approach.
Provenance Tracking: Ensures every claim is attributed with source, method, and confidence metadata.
Use Cases: Ideal for software development, system administration, and technical troubleshooting scenarios.

Quick Start

Use the /investigate slash command to initiate a systematic debugging session for a given issue.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is a systematic approach to debugging complex software issues?▼

A systematic debugging approach applies structured problem-solving workflows and root-cause analysis to identify and resolve technical issues efficiently. It moves beyond trial-and-error by tracking provenance for every claim.

How do I perform root-cause analysis for technical troubleshooting?▼

You can perform root-cause analysis by initiating a structured debugging session using the /investigate command. This applies six problem-solving workflows to trace complex technical issues to their source.

Can I use this systematic debugging framework for system administration tasks?▼

Yes, this systematic debugging framework is ideal for system administration and software development scenarios. It provides structured workflows for resolving complex technical issues across these environments.

What's the best way to track evidence during a root-cause analysis?▼

The best way to track evidence is using an Obsidian vault-based shared memory with attestation. This ensures every claim is attributed with its source, method, and confidence metadata for collaborative analysis.

Does this debugging framework support collaborative technical troubleshooting?▼

Yes, it supports collaborative troubleshooting through an investigation board that utilizes shared memory and attestation. This allows teams to systematically analyze complex issues together while maintaining evidence provenance.

How many structured problem-solving workflows are included for debugging?▼

Six structured problem-solving workflows are included for debugging and root-cause analysis. These workflows guide the systematic identification and resolution of complex technical issues.