skills.rest
dzackgarza
dzackgarzaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-deduction

Structure hypotheses and scratchpad reasoning to debug complex problems systematically.

1|Updated Feb 24, 2026
Search Tags:#debugging#problem-solving#scratchpad#root-cause#log-analysis#experiments#hypotheses
One-click install
npx skills add https://github.com/dzackgarza/ai --skill systematic-deduction
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-deduction
Source: https://github.com/dzackgarza/ai/tree/main/opencode/skills/systematic-deduction
Command: npx skills add https://github.com/dzackgarza/ai --skill systematic-deduction

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Deduction provides a disciplined framework for solving complex problems by capturing hypotheses, reasoning steps, and experiments in a reproducible scratchpad.

Core Features & Use Cases

  • Structured hypothesis tracking: maintain a living table of hypotheses, evidence, status (active/eliminated/proven), and linked experiments.
  • Scratchpad-driven debugging: encourage explicit reasoning with axioms, inferences, and test plans to isolate root causes.
  • End-to-end problem solving: from problem statement to best explanation, with iterative validation and elimination to conserve cognitive effort in multi-variable scenarios.

Quick Start

Document the problem, enumerate hypotheses, and outline experiments in the scratchpad to begin systematic deduction.

Frequently Asked Questions about systematic-deduction

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

FAQPage Schema
How do I systematically debug complex problems with multiple variables?▼

Systematic debugging uses a scratchpad to structure hypotheses, track evidence status, and log experiments, conserving cognitive effort in multi-variable investigations to isolate root causes.

What is the best way to track debugging hypotheses and log analysis results?▼

Hypothesis tracking maintains a living table of hypotheses, evidence, status (active/eliminated/proven), and linked experiments to organize log analysis and progress toward a proven explanation.

How do I perform root-cause analysis using structured reasoning steps?▼

Root-cause analysis uses a scratchpad to define axioms for elimination, outline explicit experiments, and iteratively validate inferences, moving from problem statement to best explanation.

Does this structured debugging approach work for code, logs, and systems investigations?▼

Structured debugging applies to multi-variable investigations across code, logs, and systems, using explicit reasoning with axioms and test plans to isolate root causes in any environment.

When do I need a scratchpad-driven approach for problem-solving?▼

A scratchpad-driven approach is needed for complex problem-solving where capturing reasoning steps, iterative validation, and elimination are required to reach a reproducible proven explanation.

What are the limitations of hypothesis tracking for debugging complex systems?▼

Hypothesis tracking requires manual documentation of axioms, inferences, and test plans in a scratchpad, meaning success depends on the discipline of maintaining the experiments log accurately.

Related Skills

Explore More Software Engineering Skills→
proyecto26proyecto26
42

requirements-scoping

Structure ambiguous system design prompts into functional requirements, non-functional constraints, and out-of-scope boundaries.

Official
Intermediate
fmflurryfmflurry
171

runtimeerror-http-localhost-error-resolution

Identify and resolve recurring runtime errors with a structured error-resolution pattern.

Community
Intermediate
ppiankovppiankov

logtap

Captures, triages, and analyzes ephemeral Kubernetes logs in real-time via CLI and sidecar injection.

Community
Advanced
YangYuS8YangYuS8

systematic-debugging

Identify and isolate root causes of bugs before proposing fixes.

Community
Advanced