/understand
Deep understanding mode (nemawashi) - exhaustive context-gathering before action
$ npx -y skills add bjcoombs/ai-native-toolkit --skill understand --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/understand
Context preview
The summary Claude sees to decide when to auto-load this skill.
Deep understanding mode (nemawashi) - exhaustive context-gathering before action
SKILL.md
understand.SKILL.mdname: 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:
Read more
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:
A Claude Code plugin - and a set of standalone skills for any AI assistant: skills and agents for AI-native development. In Claude Code it runs locally against your own codebase using whichever model you already pay for.
Repo: bjcoombs/ai-native-toolkit
Other skills on ai-native-toolkit.
ab-equivalence
Compare two versions of an LLM-directed document - an original (teacher) and a candidate…
assess-findings
Renders the /assess report from the deterministic run-context.json and the layer scorecard -…
assess-pr
The /assess end-of-run offers - open a PR with the report, track the Top 3 Actions in the…
assess
Assess a codebase's readiness for AI agent contributors using the layered contract model, and…

