ambiguity-and-learning

name	ambiguity-and-learning
description	Use first for ambiguous failures, messy project context, surprising results, repeated failures, postmortems, or contested product and architecture framing.

Ambiguity and Learning

Use first for ambiguous failures, messy project context, surprising results, repeated failures, postmortems, or contested product and architecture framing. This is a router skill: use it to select the smallest relevant leaf skill, then read that leaf skill before doing the work.

Route First

Do not pick a design leaf until the uncertainty shape is clear: cues, surprise, repeated governing assumption, or stakeholder conflict.

1. Restate the user's task as one concrete force or uncertainty.
2. Choose the first route that directly names that force.
3. Read the selected linked leaf SKILL.md before implementing, reviewing, or advising.
4. Load a second leaf only when the task has two independent forces that both affect the outcome.
5. If no route fits, continue without a leaf skill and say the category did not match.

Routes

Leaf Skill	Use When
sensemaking	Use when logs, errors, reports, or legacy context need a plausible working story before action.
reflective-practice	Use when a surprising result during work should reframe the next move.
double-loop-learning	Use when repeated failures point to a bad assumption, default, policy, metric, or governing variable.