skills.rest
leynos
leynosCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

hypothesis-debugging

Formulate falsifiable debugging hypotheses and plan falsification tests for software issues.

2|1|Updated Jun 13, 2025
Search Tags:#planning#debugging#documentation#root-cause-analysis#hypotheses#falsification
One-click install
npx skills add https://github.com/leynos/agent-helper-scripts --skill hypothesis-debugging
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hypothesis-debugging
Source: https://github.com/leynos/agent-helper-scripts/tree/main/skills/hypothesis-debugging
Command: npx skills add https://github.com/leynos/agent-helper-scripts --skill hypothesis-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Structured debugging through hypothesis formation and falsification planning to identify root causes without performing the investigation directly.

Core Features & Use Cases

  • Generates a hypothesis document listing candidate root causes and actionable falsification plans.
  • Designs deterministic falsification tests with clear predictions and tooling requirements.
  • Outputs a debugging plan document (assets/debugging-plan.md) for execution by another agent.

Quick Start

Generate a structured debugging plan that lists candidate root causes and falsification tests for a given issue.

Frequently Asked Questions about hypothesis-debugging

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

FAQPage Schema
What is hypothesis-based debugging and how does falsification help find root causes?▼

Hypothesis-based debugging formulates candidate root causes as structured hypotheses and designs falsification tests to eliminate incorrect explanations. Falsification planning systematically narrows down root causes without performing the investigation directly.

How do I create a structured debugging plan for an unclear software failure?▼

Create a structured debugging plan by gathering context on symptoms and reproduction conditions, generating 1-5 falsifiable hypotheses, designing deterministic tests with clear predictions, and saving the debugging plan document for execution.

Can I use this structured debugging approach for any software system or issue?▼

Use this structured debugging approach across software systems by analyzing symptoms, reproduction conditions, recent changes, and artefacts. It requires gathering context about the specific issue before generating falsifiable hypotheses and a debugging plan.

Does this debugging method run the tests and fix the bug automatically?▼

No, this debugging method does not run tests or fix bugs automatically. It outputs a debugging plan document with candidate root causes and falsification tests designed for execution by another agent.

What's the best way to document root-cause analysis for complex bugs?▼

Document root-cause analysis by outputting a markdown debugging plan listing candidate root causes, precise falsification tests, predictions, and tooling requirements. This structured document captures the investigation plan for later execution.

Related Skills

Explore More Software Engineering Skills→
geoffreywoogeoffreywoo

investigate

Guide systematic debugging by collecting symptoms and inspecting code to identify root causes.

Community
Advanced
mnthemnthe

debug

Guide systematic debugging workflows to reproduce, analyze, fix, and verify errors.

Community
Basic
xiaoshuangLixiaoshuangLi
1

debugging

Diagnose software defects through reproduction, hypothesis testing, and verification.

Community
Intermediate
yashs33244yashs33244
1

investigate

Diagnose failures through systematic root-cause investigation across four phases.

Community
Advanced