From 95704f90445266bd5a9df83d65b013cbde290960 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 12 Nov 2026 12:33:01 -0800 Subject: [PATCH 1/8] feat(skills): /quest-run and /quest-complete plan the follow-ups they surfaced When a run finishes, it runs /quest-plan on each problem it surfaced that no quest or open PR owns, in the repository whose quest tree owns it, instead of only offering to. Co-Authored-By: Claude Opus 5.5 --- assets/skills/complete.md | 2 +- assets/skills/run.md | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/assets/skills/complete.md b/assets/skills/complete.md index 7c436838..acd0f208 100644 --- a/assets/skills/complete.md +++ b/assets/skills/complete.md @@ -4,5 +4,5 @@ guide: Summaries skills: run --- -Run only the Pull requests part of `/quest-run` below, with its loop's rounds: refresh the open PRs as sub-agents report, and stop once every PR in scope is decided and every sub-agent has reported. +Run only the Pull requests part of `/quest-run` below, with its loop's rounds: refresh the open PRs as sub-agents report, and stop once every PR in scope is decided and every sub-agent has reported, then plan its follow-ups as the loop's finish describes. Start no quests, and wait on no PR. diff --git a/assets/skills/run.md b/assets/skills/run.md index caf1c817..0626a2d7 100644 --- a/assets/skills/run.md +++ b/assets/skills/run.md @@ -69,6 +69,7 @@ A usage or rate limit is waited out until its reset; it never ends the run. Finish once nothing is running, no queued merge would make a quest ready, and every PR left needs the user or a later round. Write the final summary so a fresh session can act on it, with each open decision's options beside your recommendation. +Then run `/quest-plan` on each problem the run surfaced that no quest or open PR owns, such as a blocker agents hit, in the repository whose quest tree owns it; a PR's own `## Follow-ups` are already quests. Besides the guide's controls, answer "decisions": ask every pending question now, in one batch, such as before the user steps away; the loop continues after. On "finish up", still run `/quest-merge` when a picked PR's sub-agent reports, but dispatch nothing it hands back, and list each pick left standing. From dda5cc23bdb72a5ab0347e7620d88462bdb6626b Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 12 Nov 2026 12:41:47 -0800 Subject: [PATCH 2/8] fix(skills): plan before the summary, include other trees' follow-ups, update descriptions Co-Authored-By: Claude Opus 5.5 --- .agents/skills/quest-complete/SKILL.md | 2 +- .claude/skills/quest-complete/SKILL.md | 2 +- README.md | 2 +- assets/skills/complete.md | 4 ++-- assets/skills/run.md | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/.agents/skills/quest-complete/SKILL.md b/.agents/skills/quest-complete/SKILL.md index 59f863c3..d84d4b0f 100644 --- a/.agents/skills/quest-complete/SKILL.md +++ b/.agents/skills/quest-complete/SKILL.md @@ -1,6 +1,6 @@ --- name: quest-complete -description: Decide which open PRs to merge, then queue them. +description: Decide which open PRs to merge, queue them, then plan the run's follow-ups. --- Run `quest skill complete` and follow its output. diff --git a/.claude/skills/quest-complete/SKILL.md b/.claude/skills/quest-complete/SKILL.md index 4da3e568..029a7fa1 100644 --- a/.claude/skills/quest-complete/SKILL.md +++ b/.claude/skills/quest-complete/SKILL.md @@ -1,6 +1,6 @@ --- name: quest-complete -description: Decide which open PRs to merge, then queue them. +description: Decide which open PRs to merge, queue them, then plan the run's follow-ups. allowed-tools: Bash(quest skill complete) PowerShell(quest skill complete) --- diff --git a/README.md b/README.md index 33904db8..848e74fd 100644 --- a/README.md +++ b/README.md @@ -1841,7 +1841,7 @@ arrives with the guide sections and other skills it builds on, in one call: | `quest-iterate` | Iterate on an open PR to settle its open decisions, fix CI and review findings, and push. | | `quest-review` | Review a PR's branch locally with a model other than its latest writer, then mark it ready for review. | | `quest-merge` | Queue a PR to land, running `quest-iterate` first when it needs work. | -| `quest-complete` | Run only `quest-run`'s PR decisions: decide which open PRs to merge, then queue them. | +| `quest-complete` | Run only `quest-run`'s PR decisions: decide which open PRs to merge, queue them, then plan the follow-ups the run found. | | `quest-run` | Orchestrate a project from one session: start ready quests and take PRs to merge in a loop, until only your decisions remain. | | `quest-afk` | Keep a session such as `quest-run` going while you are away: it acts on its recommendations, defers merges, and walks you through the rest when you return. | | `quest-unblock` | Settle what quests and draft PRs wait on you, and clear waits that have resolved. | diff --git a/assets/skills/complete.md b/assets/skills/complete.md index acd0f208..83f9b715 100644 --- a/assets/skills/complete.md +++ b/assets/skills/complete.md @@ -1,8 +1,8 @@ --- -description: Decide which open PRs to merge, then queue them. +description: Decide which open PRs to merge, queue them, then plan the run's follow-ups. guide: Summaries skills: run --- -Run only the Pull requests part of `/quest-run` below, with its loop's rounds: refresh the open PRs as sub-agents report, and stop once every PR in scope is decided and every sub-agent has reported, then plan its follow-ups as the loop's finish describes. +Run only the Pull requests part of `/quest-run` below, with its loop's rounds: refresh the open PRs as sub-agents report, and stop once every PR in scope is decided and every sub-agent has reported, then plan its follow-ups and write the summary as the loop's finish describes. Start no quests, and wait on no PR. diff --git a/assets/skills/run.md b/assets/skills/run.md index 0626a2d7..141096fd 100644 --- a/assets/skills/run.md +++ b/assets/skills/run.md @@ -68,8 +68,8 @@ Never wait on any other PR, and read none between rounds: list each PR left for A usage or rate limit is waited out until its reset; it never ends the run. Finish once nothing is running, no queued merge would make a quest ready, and every PR left needs the user or a later round. +Then run `/quest-plan` on the run's follow-ups, each in the repository whose quest tree owns it: problems it surfaced that no quest or open PR owns, such as a blocker agents hit, and PR follow-ups left for another repository's quest tree. Write the final summary so a fresh session can act on it, with each open decision's options beside your recommendation. -Then run `/quest-plan` on each problem the run surfaced that no quest or open PR owns, such as a blocker agents hit, in the repository whose quest tree owns it; a PR's own `## Follow-ups` are already quests. Besides the guide's controls, answer "decisions": ask every pending question now, in one batch, such as before the user steps away; the loop continues after. On "finish up", still run `/quest-merge` when a picked PR's sub-agent reports, but dispatch nothing it hands back, and list each pick left standing. From 45aedbea6f4a40d924cb5b22977d49bc93404d65 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 12 Nov 2026 12:45:16 -0800 Subject: [PATCH 3/8] fix(skills): plan only merged PRs' kept follow-ups, and nothing on finish up Co-Authored-By: Claude Opus 5.5 --- assets/skills/run.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/assets/skills/run.md b/assets/skills/run.md index 141096fd..d0c5d34c 100644 --- a/assets/skills/run.md +++ b/assets/skills/run.md @@ -68,8 +68,8 @@ Never wait on any other PR, and read none between rounds: list each PR left for A usage or rate limit is waited out until its reset; it never ends the run. Finish once nothing is running, no queued merge would make a quest ready, and every PR left needs the user or a later round. -Then run `/quest-plan` on the run's follow-ups, each in the repository whose quest tree owns it: problems it surfaced that no quest or open PR owns, such as a blocker agents hit, and PR follow-ups left for another repository's quest tree. +Then run `/quest-plan` on the run's follow-ups, each in the repository whose quest tree owns it: problems it surfaced that no quest or open PR owns, such as a blocker agents hit, and the kept follow-ups merged PRs left for another repository's quest tree. Write the final summary so a fresh session can act on it, with each open decision's options beside your recommendation. Besides the guide's controls, answer "decisions": ask every pending question now, in one batch, such as before the user steps away; the loop continues after. -On "finish up", still run `/quest-merge` when a picked PR's sub-agent reports, but dispatch nothing it hands back, and list each pick left standing. +On "finish up", still run `/quest-merge` when a picked PR's sub-agent reports, but dispatch nothing it hands back and plan nothing, and list each pick left standing and each follow-up left to plan. From 08794789a77d9a36b72969d3898537caf48ea02d Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 12 Nov 2026 13:03:17 -0800 Subject: [PATCH 4/8] fix(skills): plan the kept cross-repository follow-ups of every PR picked to merge Co-Authored-By: Claude Opus 5.5 --- assets/skills/run.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/assets/skills/run.md b/assets/skills/run.md index d0c5d34c..3e10feb5 100644 --- a/assets/skills/run.md +++ b/assets/skills/run.md @@ -68,7 +68,7 @@ Never wait on any other PR, and read none between rounds: list each PR left for A usage or rate limit is waited out until its reset; it never ends the run. Finish once nothing is running, no queued merge would make a quest ready, and every PR left needs the user or a later round. -Then run `/quest-plan` on the run's follow-ups, each in the repository whose quest tree owns it: problems it surfaced that no quest or open PR owns, such as a blocker agents hit, and the kept follow-ups merged PRs left for another repository's quest tree. +Then run `/quest-plan` on the run's follow-ups, each in the repository whose quest tree owns it: problems it surfaced that no quest or open PR owns, such as a blocker agents hit, and the kept follow-ups that PRs picked to merge left for another repository's quest tree. Write the final summary so a fresh session can act on it, with each open decision's options beside your recommendation. Besides the guide's controls, answer "decisions": ask every pending question now, in one batch, such as before the user steps away; the loop continues after. From b870fc3ebeeee27a2870b357d0a4dfa77c429d80 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 12 Nov 2026 13:18:02 -0800 Subject: [PATCH 5/8] fix(skills): plan this run's own picks' follow-ups; describe the planning in quest-run Co-Authored-By: Claude Opus 5.5 --- .agents/skills/quest-run/SKILL.md | 2 +- .claude/skills/quest-run/SKILL.md | 2 +- README.md | 2 +- assets/skills/run.md | 4 ++-- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/.agents/skills/quest-run/SKILL.md b/.agents/skills/quest-run/SKILL.md index 3396859e..c3e8d875 100644 --- a/.agents/skills/quest-run/SKILL.md +++ b/.agents/skills/quest-run/SKILL.md @@ -1,6 +1,6 @@ --- name: quest-run -description: Run a project's quest work from one session, starting ready quests and taking open PRs to merge in a loop until only the user's decisions remain. +description: Run a project's quest work from one session, starting ready quests and taking open PRs to merge in a loop until only the user's decisions remain, then planning the follow-ups the run found. --- Run `quest skill run` and follow its output. diff --git a/.claude/skills/quest-run/SKILL.md b/.claude/skills/quest-run/SKILL.md index 42c43ae0..5dddb270 100644 --- a/.claude/skills/quest-run/SKILL.md +++ b/.claude/skills/quest-run/SKILL.md @@ -1,6 +1,6 @@ --- name: quest-run -description: Run a project's quest work from one session, starting ready quests and taking open PRs to merge in a loop until only the user's decisions remain. +description: Run a project's quest work from one session, starting ready quests and taking open PRs to merge in a loop until only the user's decisions remain, then planning the follow-ups the run found. allowed-tools: Bash(quest skill run) PowerShell(quest skill run) --- diff --git a/README.md b/README.md index 848e74fd..bbbc2665 100644 --- a/README.md +++ b/README.md @@ -1842,7 +1842,7 @@ arrives with the guide sections and other skills it builds on, in one call: | `quest-review` | Review a PR's branch locally with a model other than its latest writer, then mark it ready for review. | | `quest-merge` | Queue a PR to land, running `quest-iterate` first when it needs work. | | `quest-complete` | Run only `quest-run`'s PR decisions: decide which open PRs to merge, queue them, then plan the follow-ups the run found. | -| `quest-run` | Orchestrate a project from one session: start ready quests and take PRs to merge in a loop, until only your decisions remain. | +| `quest-run` | Orchestrate a project from one session: start ready quests and take PRs to merge in a loop, until only your decisions remain, then plan the follow-ups it found. | | `quest-afk` | Keep a session such as `quest-run` going while you are away: it acts on its recommendations, defers merges, and walks you through the rest when you return. | | `quest-unblock` | Settle what quests and draft PRs wait on you, and clear waits that have resolved. | | `quest-delete` | Abandon a quest, deleting it in its own PR. | diff --git a/assets/skills/run.md b/assets/skills/run.md index 3e10feb5..fdb97095 100644 --- a/assets/skills/run.md +++ b/assets/skills/run.md @@ -1,5 +1,5 @@ --- -description: Run a project's quest work from one session, starting ready quests and taking open PRs to merge in a loop until only the user's decisions remain. +description: Run a project's quest work from one session, starting ready quests and taking open PRs to merge in a loop until only the user's decisions remain, then planning the follow-ups the run found. guide: Creation, Coordination, Summaries, Questions skills: grill, merge --- @@ -68,7 +68,7 @@ Never wait on any other PR, and read none between rounds: list each PR left for A usage or rate limit is waited out until its reset; it never ends the run. Finish once nothing is running, no queued merge would make a quest ready, and every PR left needs the user or a later round. -Then run `/quest-plan` on the run's follow-ups, each in the repository whose quest tree owns it: problems it surfaced that no quest or open PR owns, such as a blocker agents hit, and the kept follow-ups that PRs picked to merge left for another repository's quest tree. +Then run `/quest-plan` on the run's follow-ups, each in the repository whose quest tree owns it: problems it surfaced that no quest or open PR owns, such as a blocker agents hit, and the follow-ups kept in this run's own merge picks, landed or queued, for another repository's quest tree. Write the final summary so a fresh session can act on it, with each open decision's options beside your recommendation. Besides the guide's controls, answer "decisions": ask every pending question now, in one batch, such as before the user steps away; the loop continues after. From 9438178261593e36750fd70c03467b09b3d7b8f9 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 12 Nov 2026 13:21:34 -0800 Subject: [PATCH 6/8] fix(skills): plan every own pick's kept follow-ups, whatever the PR's state Co-Authored-By: Claude Opus 5.5 --- assets/skills/run.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/assets/skills/run.md b/assets/skills/run.md index fdb97095..0360448d 100644 --- a/assets/skills/run.md +++ b/assets/skills/run.md @@ -68,7 +68,7 @@ Never wait on any other PR, and read none between rounds: list each PR left for A usage or rate limit is waited out until its reset; it never ends the run. Finish once nothing is running, no queued merge would make a quest ready, and every PR left needs the user or a later round. -Then run `/quest-plan` on the run's follow-ups, each in the repository whose quest tree owns it: problems it surfaced that no quest or open PR owns, such as a blocker agents hit, and the follow-ups kept in this run's own merge picks, landed or queued, for another repository's quest tree. +Then run `/quest-plan` on the run's follow-ups, each in the repository whose quest tree owns it: problems it surfaced that no quest or open PR owns, such as a blocker agents hit, and the follow-ups kept in each of this run's own merge picks for another repository's quest tree, whatever the PR's state. Write the final summary so a fresh session can act on it, with each open decision's options beside your recommendation. Besides the guide's controls, answer "decisions": ask every pending question now, in one batch, such as before the user steps away; the loop continues after. From ebfe285a1831cc663801515436905dceffe5ab9b Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 12 Nov 2026 16:31:50 -0800 Subject: [PATCH 7/8] skills: plan follow-ups in the owning checkout while the pick stands Co-Authored-By: Claude Opus 5.5 --- assets/skills/run.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/assets/skills/run.md b/assets/skills/run.md index b5df6a64..c2b3978a 100644 --- a/assets/skills/run.md +++ b/assets/skills/run.md @@ -68,8 +68,8 @@ Never wait on any other PR, and read none between rounds: list each PR left for A usage or rate limit is waited out until its reset; it never ends the run. Finish once nothing is running, no queued merge would make a quest ready, and every PR left needs the user or a later round. -Then run `/quest-plan` on the run's follow-ups, each in the repository whose quest tree owns it: problems it surfaced that no quest or open PR owns, such as a blocker agents hit, and the follow-ups kept in each of this run's own merge picks for another repository's quest tree, whatever the PR's state. -Write the final summary so a fresh session can act on it, with each open decision's options beside your recommendation. +Then run `/quest-plan` on the run's follow-ups, each in a checkout of the repository whose quest tree owns it: problems it surfaced that no quest or open PR owns, such as a blocker agents hit, and the follow-ups kept in each of this run's own merge picks for another repository's quest tree while the pick stands, whatever the PR's state. +Write the final summary, naming those plan PRs, so a fresh session can act on it, with each open decision's options beside your recommendation. Besides the guide's controls, answer "decisions": ask every pending question now, in one batch, such as before the user steps away; the loop continues after. On "finish up", still run `/quest-merge` when a picked PR's sub-agent reports, but dispatch nothing it hands back and plan nothing, and list each pick left standing and each follow-up left to plan. From df60ab6e8915e262d0faccbeeeab296cf6597be0 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 12 Nov 2026 16:42:29 -0800 Subject: [PATCH 8/8] skills: keep landed picks' follow-ups and say which follow-ups get planned Co-Authored-By: Claude Opus 5.5 --- .agents/skills/quest-complete/SKILL.md | 2 +- .agents/skills/quest-run/SKILL.md | 2 +- .claude/skills/quest-complete/SKILL.md | 2 +- .claude/skills/quest-run/SKILL.md | 2 +- README.md | 4 ++-- assets/skills/complete.md | 2 +- assets/skills/run.md | 4 ++-- 7 files changed, 9 insertions(+), 9 deletions(-) diff --git a/.agents/skills/quest-complete/SKILL.md b/.agents/skills/quest-complete/SKILL.md index 8da11600..0f2b4fe5 100644 --- a/.agents/skills/quest-complete/SKILL.md +++ b/.agents/skills/quest-complete/SKILL.md @@ -1,6 +1,6 @@ --- name: quest-complete -description: Decide which open PRs to merge and settle what quests and drafts wait on, queue the merges, then plan the run's follow-ups. +description: Decide which open PRs to merge and settle what quests and drafts wait on, queue the merges, then plan the follow-ups no quest owns yet. --- Run `quest skill complete` and follow its output. diff --git a/.agents/skills/quest-run/SKILL.md b/.agents/skills/quest-run/SKILL.md index c3e8d875..ea7aefcf 100644 --- a/.agents/skills/quest-run/SKILL.md +++ b/.agents/skills/quest-run/SKILL.md @@ -1,6 +1,6 @@ --- name: quest-run -description: Run a project's quest work from one session, starting ready quests and taking open PRs to merge in a loop until only the user's decisions remain, then planning the follow-ups the run found. +description: Run a project's quest work from one session, starting ready quests and taking open PRs to merge in a loop until only the user's decisions remain, then planning the follow-ups no quest owns yet. --- Run `quest skill run` and follow its output. diff --git a/.claude/skills/quest-complete/SKILL.md b/.claude/skills/quest-complete/SKILL.md index 3e6d7aba..d1a4ca4f 100644 --- a/.claude/skills/quest-complete/SKILL.md +++ b/.claude/skills/quest-complete/SKILL.md @@ -1,6 +1,6 @@ --- name: quest-complete -description: Decide which open PRs to merge and settle what quests and drafts wait on, queue the merges, then plan the run's follow-ups. +description: Decide which open PRs to merge and settle what quests and drafts wait on, queue the merges, then plan the follow-ups no quest owns yet. allowed-tools: Bash(quest skill complete) PowerShell(quest skill complete) --- diff --git a/.claude/skills/quest-run/SKILL.md b/.claude/skills/quest-run/SKILL.md index 5dddb270..425f6716 100644 --- a/.claude/skills/quest-run/SKILL.md +++ b/.claude/skills/quest-run/SKILL.md @@ -1,6 +1,6 @@ --- name: quest-run -description: Run a project's quest work from one session, starting ready quests and taking open PRs to merge in a loop until only the user's decisions remain, then planning the follow-ups the run found. +description: Run a project's quest work from one session, starting ready quests and taking open PRs to merge in a loop until only the user's decisions remain, then planning the follow-ups no quest owns yet. allowed-tools: Bash(quest skill run) PowerShell(quest skill run) --- diff --git a/README.md b/README.md index 78f6ff77..65c8e3cf 100644 --- a/README.md +++ b/README.md @@ -1867,8 +1867,8 @@ arrives with the guide sections and other skills it builds on, in one call: | `quest-iterate` | Iterate on an open PR to settle its open decisions, fix CI and review findings, and push. | | `quest-review` | Review a PR's branch locally with a model other than its latest writer, then mark it ready for review. | | `quest-merge` | Queue a PR to land, running `quest-iterate` first when it needs work. | -| `quest-complete` | Run only `quest-run`'s PR decisions and settle what quests and draft PRs wait on you: decide which open PRs to merge, clear resolved waits, queue the merges, then plan the follow-ups the run found. | -| `quest-run` | Orchestrate a project from one session: start ready quests and take PRs to merge in a loop, until only your decisions remain, then plan the follow-ups it found. | +| `quest-complete` | Run only `quest-run`'s PR decisions and settle what quests and draft PRs wait on you: decide which open PRs to merge, clear resolved waits, queue the merges, then plan the follow-ups no quest owns yet. | +| `quest-run` | Orchestrate a project from one session: start ready quests and take PRs to merge in a loop, until only your decisions remain, then plan the follow-ups no quest owns yet. | | `quest-afk` | Keep a session such as `quest-run` going while you are away: it acts on its recommendations, defers merges, and walks you through the rest when you return. | | `quest-delete` | Abandon a quest, deleting it in its own PR. | diff --git a/assets/skills/complete.md b/assets/skills/complete.md index fcbaa297..08fd5c98 100644 --- a/assets/skills/complete.md +++ b/assets/skills/complete.md @@ -1,5 +1,5 @@ --- -description: Decide which open PRs to merge and settle what quests and drafts wait on, queue the merges, then plan the run's follow-ups. +description: Decide which open PRs to merge and settle what quests and drafts wait on, queue the merges, then plan the follow-ups no quest owns yet. guide: Format, Deletion, Summaries skills: run --- diff --git a/assets/skills/run.md b/assets/skills/run.md index c2b3978a..942f969c 100644 --- a/assets/skills/run.md +++ b/assets/skills/run.md @@ -1,5 +1,5 @@ --- -description: Run a project's quest work from one session, starting ready quests and taking open PRs to merge in a loop until only the user's decisions remain, then planning the follow-ups the run found. +description: Run a project's quest work from one session, starting ready quests and taking open PRs to merge in a loop until only the user's decisions remain, then planning the follow-ups no quest owns yet. guide: Creation, Coordination, Summaries, Questions skills: grill, merge --- @@ -68,7 +68,7 @@ Never wait on any other PR, and read none between rounds: list each PR left for A usage or rate limit is waited out until its reset; it never ends the run. Finish once nothing is running, no queued merge would make a quest ready, and every PR left needs the user or a later round. -Then run `/quest-plan` on the run's follow-ups, each in a checkout of the repository whose quest tree owns it: problems it surfaced that no quest or open PR owns, such as a blocker agents hit, and the follow-ups kept in each of this run's own merge picks for another repository's quest tree while the pick stands, whatever the PR's state. +Then run `/quest-plan` on the run's follow-ups, each in a checkout of the repository whose quest tree owns it: problems it surfaced that no quest or open PR owns, such as a blocker agents hit, and the follow-ups kept in each of this run's own merge picks for another repository's quest tree, landed or not, unless the user withdrew the pick. Write the final summary, naming those plan PRs, so a fresh session can act on it, with each open decision's options beside your recommendation. Besides the guide's controls, answer "decisions": ask every pending question now, in one batch, such as before the user steps away; the loop continues after.