structured-analyze

What problem does it solve?

This Skill eliminates the inefficiency of unstructured, trial-and-error technical troubleshooting that wastes hours when diagnosing software anomalies like crashes, memory leaks, performance degradation, and deadlocks, replacing random guesswork with a clear, step-by-step structured framework.

Core Features & Use Cases

• 5-Step Structured Diagnosis Workflow: Follows the proven process of boundary convergence → branch diagnosis → hypothesis validation → evidence chain → solution decision to systematically narrow down root causes.
• 4-Layer Boundary Prioritization: Quickly rules out irrelevant fault domains by checking input, software, algorithm, and hardware layers in priority order, avoiding wasted effort on unrelated code.
• Parallel Hypothesis Validation: Tests independent root cause hypotheses simultaneously instead of serial trial-and-error, significantly cutting diagnosis time.
• Evidence-Based Confidence Scoring: All conclusions are anchored to specific evidence with explicit confidence levels, eliminating vague guesses. Common use cases include debugging production crashes, memory leaks, and performance issues; performing root cause analysis for technical incidents; and guiding junior developers through systematic bug troubleshooting.

Quick Start

Use the structured-analyze skill to diagnose the root cause of the intermittent crash that occurs when users upload files larger than 100MB, starting by confirming what evidence you currently have available.