This skill provides a structured framework for creating high-quality debugging documentation tailored to how developers actually work. Instead of organizing guides by obscure root causes, it focuses on observable symptoms—the specific errors or behaviors a developer sees. It guides users through creating Quick Diagnosis tables, systematic investigation strategies, and comprehensive solution catalogs. By incorporating runnable commands, probability-ranked causes, and clear escalation paths, it ensures that project troubleshooting guides are actionable, searchable, and effective at reducing resolution time.
Key Features
014 GitHub stars
02Quick Diagnosis table templates with priority indicators
03Symptom-based documentation architecture
04Structured 'What You See' to 'Solution' mapping
05Systematic investigation strategy development
06Standardized escalation and prevention guidance
