Where are the problem-solving reports stored?

All analysis, hypotheses, and resolution reports are stored locally in the .claude/problem-solving/ directory in Markdown and JSON formats.

What problem-solving techniques does the solve skill support?

The skill supports various systematic methodologies including 5 Whys, Root Cause Analysis (RCA), Hypothesis-driven testing, and Binary Search to pinpoint errors.

How does this improve the standard Claude coding experience?

Instead of just writing code, it enforces a 'Code Assurance Layer' that validates changes through TDD and documents the logic behind every fix for future reference.

Does it integrate with my existing build and test logs?

Yes, it can receive build error logs and QA failure data as input to trigger the escalation and resolution process automatically.

Calab Systematic Problem Solver

Name: Calab Systematic Problem Solver
Author: Wondermove-Inc

byWondermove-Inc

•

Developer Tools

Analyzes and resolves complex code issues using structured methodologies like Root Cause Analysis and 5 Whys.

The Calab Solve skill is a core component of the Code Assurance Layer for AI Building, designed to replace trial-and-error debugging with a rigorous, six-stage problem-solving framework. It orchestrates specialized agents to define problems, gather data, analyze root causes using techniques like 5 Whys or hypothesis testing, and implement verified fixes through Test-Driven Development (TDD). By maintaining a persistent knowledge base of solved issues, it ensures that your codebase benefits from long-term stability and documented technical insights, making it an essential tool for maintaining high-quality production environments.

Key Features

01Multi-methodology root cause analysis (RCA, 5 Whys, Binary Search)

02Comprehensive documentation of problems, hypotheses, and solutions

031 GitHub stars

04Persistent knowledge base for searching similar past issues

05Automated TDD-based bug fixing and validation chain

06Automatic escalation from build failures and QA regressions

Use Cases

01Identifying the root cause of intermittent or complex production bugs

02Systematically resolving build failures or regression test errors

03Building a searchable repository of architectural and logic fixes

Key Features

01Multi-methodology root cause analysis (RCA, 5 Whys, Binary Search)

02Comprehensive documentation of problems, hypotheses, and solutions

031 GitHub stars

04Persistent knowledge base for searching similar past issues

05Automated TDD-based bug fixing and validation chain

06Automatic escalation from build failures and QA regressions

Use Cases

01Identifying the root cause of intermittent or complex production bugs

02Systematically resolving build failures or regression test errors

03Building a searchable repository of architectural and logic fixes