Fishbone Diagram Analysis
Requirements
A problem statement to analyze
2
Get the problem statement from the user. If they haven't provided one, ask:
"What problem do you want to map out?"
Clarify the problem until it's specific and observable.
3
Propose 4-6 cause categories appropriate to the problem domain. Explain
briefly why these categories make sense. Ask if the user wants to adjust.
Use domain-appropriate categories from the guide, not generic ones.
4
Work through each category with the user. For each:
- Ask: "What in [category] could contribute to this problem?"
- Capture their answers
- Probe: "What else?" until the category feels complete
- Ask if any causes seem particularly likely (mark as primary)
Keep the pace moving—thoroughness matters but don't over-analyze minor causes.
5
Generate the fishbone analysis document:
- Clear problem statement
- All categories with their potential causes
- Primary causes marked with ⭐
- Summary of most likely contributors with reasoning
- Recommended next steps
Include the ASCII visual if the user would benefit from seeing the structure.
Present the document to the user.
To run this task you must have the following required information:
> A problem statement to analyze
If you don't have all of this information, exit here and respond asking for any extra information you require, and instructions to run this task again with ALL required information.
---
You MUST use a todo list to complete these steps in order. Never move on to one step if you haven't completed the previous step. If you have multiple read steps in a row, read them all at once (in parallel).
Add all steps to your todo list now and begin executing.
## Steps
1. [Read Fishbone Diagram Guide]: Read the documentation in: `skills/sauna/[skill_id]/references/analysis.fishbone.guide.md`
2. Get the problem statement from the user. If they haven't provided one, ask:
"What problem do you want to map out?"
Clarify the problem until it's specific and observable.
3. Propose 4-6 cause categories appropriate to the problem domain. Explain
briefly why these categories make sense. Ask if the user wants to adjust.
Use domain-appropriate categories from the guide, not generic ones.
4. Work through each category with the user. For each:
1. Ask: "What in [category] could contribute to this problem?"
2. Capture their answers
3. Probe: "What else?" until the category feels complete
4. Ask if any causes seem particularly likely (mark as primary)
Keep the pace moving—thoroughness matters but don't over-analyze minor causes.
5. Generate the fishbone analysis document:
- Clear problem statement
- All categories with their potential causes
- Primary causes marked with ⭐
- Summary of most likely contributors with reasoning
- Recommended next steps
Include the ASCII visual if the user would benefit from seeing the structure.
Present the document to the user.