failure-tracker

Track debugging failures by logging the context, root cause, solution, and prevention steps. This systematic failure documentation categorizes issues into code, pattern, tool, environment, or process types to prevent recurring mistakes.

Logging development mistakes for a retrospective requires capturing what went wrong and why. This skill provides a standard log format that integrates with retrospective processes to analyze failures and update prevention checklists.

Categorize coding errors by classifying them into code, pattern, tool, environment, or process types. This classification routes failures to the appropriate project-specific or global logs for better analysis and future prevention.

Yes, you can route failure logs to specific project directories. The routing logic directs failures to global, skill-specific, or project-specific logs based on the context, ensuring documentation is organized and accessible.

A software failure log entry should include the failure category, context, what went wrong, the root cause, the solution, and how to prevent it. This standard format ensures comprehensive documentation for future debugging.

A structured process for logging environment and tool failures prevents recurring mistakes and improves process quality. Systematic documentation ensures anyone encountering a similar issue can quickly find the root cause and resolution.