What

Temporarily hold the pending action, explain the active frontier, then prompt the user to resume work.

Trigger And Scope

Treat only an entire trimmed ? message, an explicit $what or @what invocation, and an explicit attachment of this skill as the checkpoint trigger. Do not intercept an ordinary question that merely contains ?.

When the user instead asks to re-orient around an active task after not understanding the current update, answer in the same checkpoint style without taking ownership of ordinary prose that simply includes a question mark.

Explain Annotated Passages

Review feedback, such as OpenCode Annotate's, may arrive with this skill attached and with annotations whose comment is what?. Each such annotation quotes a passage the user does not understand. Explain each quoted passage before anything else: in plain language, with more detail, a concrete example where it helps, and how it relates to the current task. Follow any instruction the feedback adds for these notes, and address its other annotations as usual.

Explain The Frontier

State the last confirmed point, current workflow and step, changed artifacts, why the state matters, and the pending next action. Preserve project terms and read the nearest CONTEXT.md when it exists.

Do not advance the workflow, delegate the pending action, or invent a new route while explaining the frontier. Keep the pending action paused at its current boundary until the user explicitly resumes it.