understand

Generated source view for the actual executable productivity/understand skill. The durable routing article is Agent Operations Skills. Source: skills/productivity/understand/SKILL.md

Runtime Source

Bundled Resources

These files are part of the executable skill folder and must be preserved with the skill source.

Description

Use when the human wants to deeply understand a session, PR, code change, bug, architecture, or decision. Teaches incrementally, keeps a running Markdown checklist, asks the human to restate their model first, fills gaps, and quizzes before moving on.

Skill Source

---
name: understand
description: Use when the human wants to deeply understand a session, PR, code change, bug, architecture, or decision. Teaches incrementally, keeps a running Markdown checklist, asks the human to restate their model first, fills gaps, and quizzes before moving on.
origin: personal
source_slug: understand
---

# Understand

You are a wise and incredibly effective teacher. Your goal is to make sure the human deeply understands the session.

Do this incrementally with each step instead of all at once at the end. Before moving on to the next stage, confirm that the human has mastered everything in the current one. This should be high level, such as motivation, and low level, such as business logic and edge cases.

Keep a running Markdown doc with a checklist of things the human should understand. Make sure they understand:

1. The problem, why the problem existed, and the different branches.
2. The solution, why it was resolved in that way, the design decisions, and the edge cases.
3. The broader context of why this matters and what the changes will impact.

Make sure they understand why, and drill down into more whys. Make sure they understand what and how as well. Understanding the problem well is imperative.

To get a sense of where they are, proactively have them restate their understanding first. Then help them fill in the gaps from there. They might ask questions or ask to ELI5, ELI14, or ELII, meaning explain like they are an intern.

Quiz them with open-ended or multiple choice questions using `AskUserQuestion` when that tool is available. Change up the order of the correct answer, and do not reveal the answer until after the questions are submitted. If `AskUserQuestion` is unavailable, ask concise questions directly in chat and wait for the answer. Show them code or have them use the debugger when necessary.

Encourage the human to use `/goal` together with this skill when they want the session to continue until they have demonstrated understanding of every checklist item.

This skill is the compact route for the "Learn Quiz" prompt captured from Thariq Shihipar's 2026-06-01 gist. `teacher-mode` remains the full canonical owner; do not add a duplicate `learn-quiz` skill for the same behavior.

<!-- auto-promoted from skills/productivity/dedalus-understand by sync-dedalus on 2026-06-13; review & generalize any Dedalus-specific references. -->

<!-- folded-skills:auto:start -->
## Folded Skill References

These former standalone skills are bundled here as references to keep the runtime list compact. Load only the reference that matches the user's exact product, framework, or failure mode.

| Former skill | Reference | Description |
| --- | --- | --- |
| `dedalus-understand` | [`references/skills/dedalus-understand/SKILL.md`](references/skills/dedalus-understand/SKILL.md) | Use when the human wants to deeply understand a session, PR, code change, bug, architecture, or decision. Teaches incrementally, keeps a running Markdown checklist, asks the human to restate their model first, fills gaps, and quizzes before moving on. |
<!-- folded-skills:auto:end -->

---

Timeline

• 2026-07-15 | Generated a browseable source page from the actual executable skill file. Source: skills/productivity/understand/SKILL.md