Mode auto-run - any request, start to finish, without waiting
The user typed /mode-auto-run <request> and walked away. Typing it is the waiver: the hook has turned auto-run on for
this session (its AUTO stamp) and opened this run's marker, every ask that marks a (Recommended) option is answered
with it, and the run goes on until its close. Auto-run outlives the run: it stays on for the session until the user
types --mode-auto-run-off after a command. The limits stay where they are - nothing outward, nothing paid. A guard's
security ask - a credential shown, work discarded, a write outside the project, a desktop launch, a protective guard
switched off - is never auto-run's to allow: take its safe option and list the act for the user in the close.
Availability - the flows this skill names are user-typed commands, installed only where the install picked them. The
Solve flow: line in context says whether the solve flow is installed here; any other flow named below is never run
from this skill, only named for the user.
When to use
- Any request typed after
/mode-auto-run: a feature, a fix, a refactor, a failing test, a question, a doc.
- Three starts run nothing - say the one line and stop:
- Only mode flags were typed (
/mode-auto-run --mode-auto-run-off, /mode-auto-run --mode-auto-run-on): the flag
switched auto-run for the session - say which way.
- The banner reads
Auto-run: OFF (no request, or another session's run holds the stamp): say why it did not start,
as the banner gives it.
- No
auto-run is ON contract line is in context (hooks off, the minimal profile, Cursor): say that auto-run did not
start because no hook ran, and stop.
The route
Say the route in one line before the work, then take it:
- A code change - the request will edit a file outside the docs root, the data root and
.claude/ (a feature,
a fix, a refactor, a failing test), whatever its size. Read the file the Solve flow: line names, whole, and
follow it as this run's flow with the request as its task, from its first step to its close: its sizing, its plan
file, its building in this chat or in seats as its recommended options say, its review and its commit checkpoint.
Its references/ and scripts/ paths sit beside that file.
- After a compaction, Read it again before the next step. The
Solve flow: line is gone by then; the file is
skills/task-solve/SKILL.md under the account's config folder, else .claude/skills/task-solve/SKILL.md in
the project.
Solve flow: not installed here, or switched off here (the project's skillOverrides) - one Left for you:
line, /task-solve <request> once it is installed or switched back on, and the close.
- A
cross size, whose row names /task-solve-cross, is the user's command: one Left for you: line,
/task-solve-cross <request>, and the close.
- Another user-typed flow's job - a version upgrade (
/task-version-upgrade), a build from scratch
(/task-build-from-scratch), a diagnosis (/issue-diagnoser), a quality loop (/loop-code-quality,
/loop-architecture-quality, /loop-test-coverage-quality), a capture (/capture-awareness, /capture-preferences,
/capture-awareness project-code-style, /capture-usage-report), a change across several parts (/task-solve-cross). Not
run here: one Left for you: line, /<that flow> <request>, and the close.
- Anything else - a question, a doc under the docs root: do it directly. A file it writes stays uncommitted and
is named in the close.
Each Left for you: command runs unattended when typed: auto-run stays on for this session, so the line says so.
The limits
mode-auto-run commits nothing itself; the solve flow's commit checkpoint does.
- Never push, merge, deploy, publish, open a PR or pay - each goes under
Left for you:.
- Work the request does not name goes in the close, each line marked
Recommended - <reason> or
Not worth it - <reason>.
- Tool permission prompts follow the user's permission mode; this skill changes none.
The close
After the flow's own close, when one ran:
Done: <what the request asked for, and whether it is met>
Changed: <files, and each commit with its subject>
Checks: <each command run, with its result line>
Decisions auto-run made for you:
- <the ask> - <the option taken>
Left for you: <each outward act, each NOT RUN and why> | none
Then delete the run marker if the flow's close left it, as the contract's item (7) says - that ends this run. Never
delete the AUTO stamp: auto-run stays on for the session until the user types --mode-auto-run-off after a command.
1---2name: mode-auto-run3description: "Use when the user types /mode-auto-run <request> - auto-run turns on for the session and the request runs to its end, each ask taking its Recommended option."4disable-model-invocation: true5metadata:6 source: https://skillmd.com/skills/envoydev/mode-auto-run7---89# Mode auto-run - any request, start to finish, without waiting1011The user typed `/mode-auto-run <request>` and walked away. Typing it is the waiver: the hook has turned auto-run on for12this session (its `AUTO` stamp) and opened this run's marker, every ask that marks a (Recommended) option is answered13with it, and the run goes on until its close. Auto-run outlives the run: it stays on for the session until the user14types `--mode-auto-run-off` after a command. The limits stay where they are - nothing outward, nothing paid. A guard's15security ask - a credential shown, work discarded, a write outside the project, a desktop launch, a protective guard16switched off - is never auto-run's to allow: take its safe option and list the act for the user in the close.1718**Availability** - the flows this skill names are user-typed commands, installed only where the install picked them. The19`Solve flow:` line in context says whether the solve flow is installed here; any other flow named below is never run20from this skill, only named for the user.2122## When to use2324- Any request typed after `/mode-auto-run`: a feature, a fix, a refactor, a failing test, a question, a doc.25- Three starts run nothing - say the one line and stop:26 - Only mode flags were typed (`/mode-auto-run --mode-auto-run-off`, `/mode-auto-run --mode-auto-run-on`): the flag27 switched auto-run for the session - say which way.28 - The banner reads `Auto-run: OFF` (no request, or another session's run holds the stamp): say why it did not start,29 as the banner gives it.30 - No `auto-run is ON` contract line is in context (hooks off, the minimal profile, Cursor): say that auto-run did not31 start because no hook ran, and stop.3233## The route3435Say the route in one line before the work, then take it:36371. **A code change** - the request will edit a file outside the docs root, the data root and `.claude/` (a feature,38 a fix, a refactor, a failing test), whatever its size. Read the file the `Solve flow:` line names, whole, and39 follow it as this run's flow with the request as its task, from its first step to its close: its sizing, its plan40 file, its building in this chat or in seats as its recommended options say, its review and its commit checkpoint.41 Its `references/` and `scripts/` paths sit beside that file.42 - After a compaction, Read it again before the next step. The `Solve flow:` line is gone by then; the file is43 `skills/task-solve/SKILL.md` under the account's config folder, else `.claude/skills/task-solve/SKILL.md` in44 the project.45 - `Solve flow: not installed here`, or `switched off here` (the project's `skillOverrides`) - one `Left for you:`46 line, `/task-solve <request>` once it is installed or switched back on, and the close.47 - A `cross` size, whose row names `/task-solve-cross`, is the user's command: one `Left for you:` line,48 `/task-solve-cross <request>`, and the close.492. **Another user-typed flow's job** - a version upgrade (`/task-version-upgrade`), a build from scratch50 (`/task-build-from-scratch`), a diagnosis (`/issue-diagnoser`), a quality loop (`/loop-code-quality`,51 `/loop-architecture-quality`, `/loop-test-coverage-quality`), a capture (`/capture-awareness`, `/capture-preferences`,52 `/capture-awareness project-code-style`, `/capture-usage-report`), a change across several parts (`/task-solve-cross`). Not53 run here: one `Left for you:` line, `/<that flow> <request>`, and the close.543. **Anything else** - a question, a doc under the docs root: do it directly. A file it writes stays uncommitted and55 is named in the close.5657Each `Left for you:` command runs unattended when typed: auto-run stays on for this session, so the line says so.5859## The limits6061- `mode-auto-run` commits nothing itself; the solve flow's commit checkpoint does.62- Never push, merge, deploy, publish, open a PR or pay - each goes under `Left for you:`.63- Work the request does not name goes in the close, each line marked `Recommended - <reason>` or64 `Not worth it - <reason>`.65- Tool permission prompts follow the user's permission mode; this skill changes none.6667## The close6869After the flow's own close, when one ran:7071```text72Done: <what the request asked for, and whether it is met>73Changed: <files, and each commit with its subject>74Checks: <each command run, with its result line>75Decisions auto-run made for you:76- <the ask> - <the option taken>77Left for you: <each outward act, each NOT RUN and why> | none78```7980Then delete the run marker if the flow's close left it, as the contract's item (7) says - that ends this run. Never81delete the `AUTO` stamp: auto-run stays on for the session until the user types `--mode-auto-run-off` after a command.