To run this task you must have the following required information:

> A problem statement or situation 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 CONSECUTIVE read steps in a row, read them all at once (in parallel). Otherwise, do not read a file until you reach that step.

Add all steps to your todo list now and begin executing.

## Steps

1. [Read 5 Whys Facilitation Guide]: Read the documentation in: `skills/sauna/[skill_id]/references/analysis.fivewhys.guide.md`

2. Get the problem statement from the user. If they haven't provided one, ask:
"What problem or situation do you want to analyze?"

Ensure the statement is specific and observable—not vague like "things aren't
working" but concrete like "our last three releases had critical bugs."


3. Begin the 5 Whys analysis. For each answer the user provides:

1. Evaluate: Is this a root cause or a symptom?
   - Symptom: Ask "Why did that happen?" to go deeper
   - Root cause: Confirm understanding and check if there are branches

2. If the answer suggests multiple causes, note the branch and explore both

3. Keep questions factual and system-focused, not blame-oriented

Continue until you reach actionable root cause(s)—typically 3-7 iterations.


4. Generate the analysis document using the format from the guide:

- Clear problem statement
- Numbered analysis chain showing each why/answer
- Any branches explored
- Root cause summary
- Specific recommended actions

Present the document to the user.


5. Save the 5 Whys analysis to `documents/work/projects/**/*.md` as a dated file
(e.g., 5whys-{problem}-{date}.md). This preserves root cause findings
for future reference.