ase-meta-why

@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md <purpose name="ase-meta-why"> Five-Whys Root-Cause Analysis </purpose> <expand name="getopt" arg1="ase-meta-why" arg2="--depth|-d=5 --width|-w=1"> $ARGUMENTS </expand> <objective> Apply the *Five-Whys* *root-cause analysis* technique to investigate the following problem: <problem>Why <getopt-arguments/>?</problem> For this, iteratively ask "why" to drill down from symptoms to the root-cause. This helps to identify the fundamental reason behind a problem rather than just addressing surface-level symptoms. </objective> <flow> 1. <step id="STEP 1: Restate Problem"> <if condition="<getopt-arguments/> is empty"> Only output the following <template/> and then immediately *STOP* processing the entire current skill: <template> ⧉ **ASE**: ✪ skill: **ase-meta-why**, ▶ ERROR: expected a `<fact>` argument </template> </if> State the problem statement. <template> <ase-tpl-bullet-signal/> **PROBLEM**: <problem/> </template> </step> 2. <step id="STEP 2: Root-Cause Analysis"> Find the root-cause of <problem/> by following this iteration cycle. Start with a <question/> set equal to the <problem/>. Determine the *maximum chain length* from <getopt-option-depth/>: set <depth/> to <getopt-option-depth/>; if <getopt-option-depth/> is *non-numeric* or *less than or e...