spec-gen-debug

Root-cause analysis is faster when you anchor debugging in structural knowledge, forming a falsifiable hypothesis before reading source. This approach uses spec-gen orient to surface candidate functions and call paths, reducing wasted exploration and guiding minimal, test-backed fixes.

Hypothesis-driven debugging requires an explicit, falsifiable hypothesis based on structural traces before editing code. After a scoped fix passes RED/GREEN verification, spec drift checks trigger, appending discovered invariants to domain specs to prevent future bug recurrence.

Tracing call paths for root-cause analysis uses spec-gen orient to surface candidate functions and domains related to a reported symptom. This structural knowledge guides reproducible bug investigation, preventing speculative edits by prioritizing architectural context over file browsing.

Spec-gen tools support RED/GREEN verification by guiding minimal edits and enforcing a failing test first. You need project root access, reproducible steps, and the ability to run tests to verify the fix passes and execute the full suite for drift checks.

Hypothesis-first debugging requires spec-gen analysis tools like orient, analyze_impact, and search_specs to be available in your repository. Without reproducible steps and project root access to run tests and MCP tools, this structural root-cause analysis workflow cannot function.

Root-cause analysis with this approach works with any testing framework as long as you have project root access and reproducible steps to run tests. It relies on spec-gen MCP tools for structural traces and RED/GREEN verification rather than a specific testing platform.