commit c5d8cf1654d77b0899338d74bc85dd06a57fb299 equwal <13551856+equwal@users.noreply.github.com> 2026-09-26 20:44:46 -0700 Add the section about more than one task to the rule The rule now tells Claude to stop only the blocked task of a request. Claude continues the other tasks while the dialog is open, and asks its questions at the end. SKILL.md has the same instructions since 17b0cae. The rule gives them to Claude before Claude loads the skill.
README.md | 1 + rules/deploy-handoff.md | 18 +++++++++++++++++- 2 files changed, 18 insertions(+), 1 deletion(-)
diff --git a/README.md b/README.md index 72e0560..112062a 100644 --- a/README.md +++ b/README.md @@ -54,6 +54,7 @@ The skill tells Claude how to hand off a step. The rule [rules/deploy-handoff.md The rule also tells Claude to: - Run a deploy command, for example `vercel deploy` or `gh release create`, when a command can do the step. The permission prompt of Claude Code is your approval. In a permission mode with no prompt, Claude asks you in the chat before a production deploy, a release, or a live payment change. +- Continue the other tasks of a request while one task waits for you in the dialog. - Drive the browser to the page of the last step, not only to the home page of a console. - Use the browser profile in which you are signed in. Claude starts a fresh profile only if you ask for it. - Push directly when you ask for a change, and open a pull request only when the repository needs one. The pull request form opens with `handoff.py pr`. diff --git a/rules/deploy-handoff.md b/rules/deploy-handoff.md index 9c53755..b4fa83a 100644 --- a/rules/deploy-handoff.md +++ b/rules/deploy-handoff.md @@ -20,7 +20,23 @@ To hand off: 1. Drive the browser as far as you can with your browser tools. 2. Use the skill. Write the title and the steps in Simplified Technical English. -3. Wait for the answer. If the answer is "done", check the result. Then continue the task. +3. While the dialog is open, continue the other tasks. If the answer is "done", check the result. Then continue the task. + +## More than one task: stop only the blocked task + +A request can have more than one task, for example a web deploy, a store release, and a payment setup. A task is blocked when it gets to a step that you cannot do. Examples: a sign-in, an account creation, a CAPTCHA, a permission prompt that the user denied, or an error that you cannot fix. + +A blocked task does not stop the other tasks. When a task is blocked: + +1. Stop that task, and each task that needs its result. +2. If the blocked step has a web page, hand it off with the skill. Run the dialog in the background. +3. Continue all the other tasks while the dialog is open. +4. When the user answers "done", check the result. Then continue the blocked task. +5. Put each question for the user at the end, after the other tasks are done or blocked. A question ends your turn and stops the other tasks. + +At the end, give the result of each task: done or blocked. For a blocked task, give the cause and the step that the user must do. + +If the user tells you to stop, stop all the tasks. ## Deploys that need no browser: run the command