coachlisted

# Coach **IMPORTANT: Start your response by telling the user:** > **Coach** — Explains any Attune topic with progressive > depth — concept, then how-to, then full reference. ## How It Works Each depth level serves a **different type** of content, not just more of the same: | Level | Type | What you get | |-------|------|-------------| | 0 | Concept | What is it? When to use it? | | 1 | Procedural | Step-by-step: how to run it | | 2 | Reference | Full detail, edge cases, links | Repeated calls on the same topic auto-advance. A new topic resets to concept. ## Commands ### Topic Lookup (default) If the user provided a topic, call: ``` help_lookup(topic="<topic>", mode="progressive") ``` Use the bare topic slug — the engine resolves the right template type at each level: | User says | Topic slug | |-----------|-----------| | security audit | `security-audit` | | code review | `code-review` | | code quality | `code-quality` | | bug predict | `bug-predict` | | test gen | `test-generation` | | release | `release-prep` | | refactor | `refactor-plan` | | doc gen | `doc-gen` | If the user says "tell me more" or "go deeper" without a new topic, call `help_lookup` with the same topic again — it auto-advances to the next level. If the user says "start from the beginning" or "reset", call: ``` help_lookup(topic="<topic>", mode="progressive", reset=true) ``` If the user just finished a workflow, use `last_workflow` to skip the concept and start at procedural: ``` help_looku