--- name: reorient description: Catch the user up on overall progress and pending decisions in the current conversation. Use for a general catch-up, not a single-item status, explanation repair or agent handoff. --- # Reorient Restore the user's bearings, usually in a short paragraph plus any choices waiting on them. Cover changes since their last message before this request, or the point they specify. Notifications and worker reports do not reset that window. Use names they recognize. Recall the objective only if it helps; skip routine steps and repeated history. Use this conversation and its directly delegated work. Prefer available evidence. Make a narrow, authorized, read-only check of the known task or artifact only when missing or stale information would change a pending decision or next action; otherwise label status as last observed. If history is unavailable, name the gap. A catch-up alone does not authorize edits, jobs, messages or resuming work. Separately requested actions keep their own authority. Summarize established progress and choices, including newly observed material facts, without reopening deliberation. Include every unresolved decision or action that actually requires the user, even if older than the recap window. Exclude answered, declined or superseded items. Keep next steps within the assigned work. An action the agent may not take is not automatically the user's task; state the relevant limit without assigning it unless the user must act now. Work the agent can finish within its authority stays with the agent. For each pending choice, give the options and the material tradeoff already established, usually in one sentence. Related choices may share an explanation if each item's differences stay visible. Preserve relevant known scope changes, running or unconfirmed work, blockers, prerequisites, irreversible effects, deadlines, costs of waiting and uncertainty. Carry forward an existing recommendation when useful; new recommendations, speculative consequences and further exploration belong only in a request for advice. Do not invent choices, approvals or chores to fill a format. Use more space when necessary to make every choice answerable. Never replace pending items with a count or hide them behind links to meet a length target. Do not impose fixed headings, nested status templates or drill-down menus; follow any user- or host-required format. If nothing changed and nothing needs the user, say so and stop. Expand history or reasoning on request.