agentleFS
kele-devkele-dev/Claude-Orchestrator-Skill/skills/autopilot/SKILL.md

autopilot

Skill10 starsChanged 2 days agoMITView on GitHub

Autonomous sequential execution under the orchestrator cost rules. One short clarification round, a PRD, then batch after batch (delegate, verify, fix) without asking between batches, until done or a cap is hit. Only runs when the user types /orchestrator:autopilot.

81 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review-bugbot, rename-chat and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • 0mlkrizzz655335vSkill

    review-bugbot

    缺陷导向代码审查。用 Bugbot 子代理找 bug。

    Also in 3 projects that use this

  • 0mlkrizzz655335vSkill

    rename-chat

    重命名当前聊天。按聊天内容改标题。"disable-model-invocation: true

    Also in 3 projects that use this

  • Tsumugii24Skill

    split-to-prs

    Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.

    Also in 4 projects that use this

  • PandelisZSkill

    update-cli-config

    View and modify Cursor CLI configuration settings in ~/.cursor/cli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.

    Also in 3 projects that use this

  • 32103210Skill

    migrate-to-skills

    Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use when you want to migrate rules or commands to skills, convert .mdc rules to SKILL.md format, or consolidate commands into the skills directory.

    Also in 3 projects that use this

  • 32103210Skill

    update-cursor-settings

    Modify Cursor/VSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.

    Also in 3 projects that use this

  • +1 more from 32103210
  • +1 more from 0mlkrizzz655335v

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 72 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the questions (if any) in one go.

    line 25
  2. Very specific:

    Verify: per modes.md (verify).

    line 34

“Common” is measured: kept by at least 6 in 10 of the 72 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Autopilot mode: autonomous batches, token-capped

Task: $ARGUMENTS

Autopilot is orchestrator:on without stopping between batches (the main session never edits). Shared mode rules (caps, fix rounds, raises, commit=batch, report, lessons): read modes.md in the orchestrator:on skill folder. Unit = group = batch.

Budget (defaults; the user may override them in the arguments, e.g. batches=8)

  • Clarification: one round only, at most 3 questions, asked at the start and only if the answers would change the design. Otherwise decide yourself and record the assumptions in the PRD.
  • Max batches: 5, raised automatically up to 8: if the plan, or work discovered on the way, needs more than 5, continue without asking, but only while every finished batch passed. Any BLOCKED batch ends the extension. If more are needed past the cap, report and ask whether to continue.
  • Max fix rounds per batch: 2, raised automatically up to 4 (see modes.md).
  • opus-reviewer: at most once on the PRD and once on the final diff, and only for large work (>5 tasks, or touches schema/auth/security). Never per batch. Not Opus-class: the orchestrator:on reviewer rules (PRD before the first delegation, final diff) apply whatever the size.
  • --dry-run: stop after stage 2 and show the PRD and batch plan.
  • commit=batch scope: per batch, after it passes verification.
  • Checkpoint timing: after every 3rd batch.
  • budget=<N>k (optional): token budget over all delegations; rules in modes.md (Budget).

1. CLARIFY

Ask the questions (if any) in one go. After the answers, do not ask again until a stop condition.

2. PRD + BATCH PLAN (main session)

  • Lessons in and PRD: per modes.md.
  • Order the work into batches by dependency. Each batch = 1-3 atomic tasks with its own verification command.
  • Show the batch list in one short block, then continue without waiting (unless --dry-run).

3. LOOP, per batch

  1. Delegate: per orchestrator:on step 3. Tasks inside a batch run sequentially, or in parallel only when they touch disjoint files.
  2. Verify: per modes.md (verify).
  3. Fix: per modes.md (fix loop, NEEDS ARCHITECTURE DECISION), at most 2 rounds (or up to 4 per modes.md).
  4. Batch passed: go straight to the next batch. Do not ask the user for confirmation between batches.

4. STOP conditions (the only times you stop or ask)

  • DONE: all batches pass and the final project-level check (full test/build/lint, if any) passes.
  • BLOCKED: a batch hit its fix cap. Do not start later batches that depend on it; report.
  • DECISION NEEDED: an architecture decision or user input that cannot be safely assumed. Stop and ask.
  • BATCH LIMIT: the batch cap was reached with work left. Report and ask whether to continue.
  • BUDGET: budget=<N>k reached; checkpoint and report per modes.md (Budget).

5. REPORT

Per modes.md: report. Unit = batch; status PASS / BLOCKED.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.