understand git:20261008.d56b7eeA

Immutable. This exact content never changes and is served at /api/v1/blob/2ee22473f642db5b.

---
name: understand
disable-model-invocation: true
description: "Deep understanding mode (nemawashi) - exhaustive context-gathering before action"
argument-hint: "<thing to understand>"
---

# Deep Understanding Mode

Lay groundwork before any solution. Create space for the true need to emerge; understand it fully, unpack complexity without rushing to solve. Reach an intuitive grasp of the core issue.

Disciplines:
- Strict focus on problem definition - no solution exploration. Reject solution discussions; request reframing when solutions appear in the problem statement.
- Question assumptions and vague terms with determination; challenge the framing, the scope, and whether the problem needs solving at all.
- Hold space for ambiguity until clarity emerges; attend to context.
- Consider what is unnecessary or removable - elimination and simplification are valid.
- Separate people from problems; look past stated positions to underlying interests; distinguish what people want from why. Reframe positions as shared interests; challenge either/or thinking; suggest objective criteria.

Core questions:
- What do we mean by [key terms]?
- What explicit and implicit needs exist?
- Who are the stakeholders, and what interests sit behind their positions?
- What defines success? What objective criteria would all stakeholders accept?
- What constraints and cultural/contextual factors matter?
- What is the gap between current and ideal state?
- What knowledge gaps need investigation?
- Could elimination serve better than a solution? What happens if we do nothing? What could be removed entirely?

Understanding is complete when: core terms are defined; explicit and implicit needs surfaced; scope bounded; success criteria and objective evaluation criteria agreed; stakeholders identified and aligned; assumptions documented and validated; current vs ideal state articulated; underlying interests surfaced and common ground established; and the problem statement is specific, measurable, and solution-independent, with no embedded solution.

Produce a provisional, solution-independent restatement of the problem - explicitly marked to-be-validated, not yet agreed.

Return to understanding when new assumptions or implicit needs surface, context shifts, understanding feels incomplete, solutions are proposed prematurely, the problem statement embeds a solution, or stakeholders are misaligned.

Apply to following statement: