SDD Root Cause Analysis & Troubleshooting FAQs

Question 1

How does this skill integrate with my existing documentation?

Accepted Answer

It references your requirements and design docs to verify if the behavior is a bug or a spec gap, and it saves analysis reports to a dedicated troubleshooting folder for future reference.

Question 2

Does this skill automatically modify my source code?

Accepted Answer

No. It follows a strict workflow where it first analyzes the problem and presents a fix strategy. It only proceeds to task creation and implementation after you have explicitly approved the plan.

Question 3

What happens if the root cause is a flaw in the design itself?

Accepted Answer

The skill identifies this as a 'Specification Bug' or 'Specification Gap' and prompts you to update the design documentation as part of the resolution process.

Question 4

What is the primary goal of the sdd-troubleshooting skill?

Accepted Answer

The primary goal is to ensure that software fixes are based on a systematic identification of the root cause rather than guesswork, while ensuring the solution aligns with the original project requirements.

Question 5

Can I use this for simple syntax errors?

Accepted Answer

While it can be used for any error, it is most effective for complex logic bugs and system failures where understanding the 'why' is just as important as the 'how' of the fix.

SDD Root Cause Analysis & Troubleshooting

SDD Root Cause Analysis & Troubleshooting

Key Features

Use Cases

Key Features

Use Cases