跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
其他技能

sw-autopilot

Use when the user wants several Superwiki tasks worked through one after another without being asked at each step (run the backlog, do all tasks of an area, keep going until done or blocked, act as orchestrator, continue a run), or invokes sw-autopilot.

mhmtsrfglu · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add mhmtsrfglu/superwiki --skill sw-autopilot

技能说明


name: sw-autopilot description: Use when the user wants several Superwiki tasks worked through one after another without being asked at each step (run the backlog, do all tasks of an area, keep going until done or blocked, act as orchestrator, continue a run), or invokes sw-autopilot.

sw-autopilot

Works through tasks in order, unattended, each one as the single-task skills run it. You are the orchestrator: subagents with clean contexts do the work; your session holds the queue, the reports and the decisions. Like a car's autopilot, the run knows its route before it engages, and hands back the wheel when it lacks the data.

Run commands from the project root. A message that continues a run starts at "Continuing a run".

The skills a run follows

Load each once and follow it for every task:

  • sw-plan-implement: step 1's check table, steps 2 and 3 (the rubric, the Route: line) and step 4's medium route (the Approach note);
  • sw-plan: steps 4 to 6 and "An agreed split", on the large route;
  • sw-implement: steps 2 to 10 and "Dispatching";
  • sw-verify: all of it, as sw-implement step 8 calls it.

This skill takes the place of their other steps.

Before the first task

  1. Scope, from the user's message: an area, a list of ids, or everything that becomes ready. An area is a task id prefix; areas in docs/.sw/config.json maps each prefix to its name, so "the backend area" is the prefix named Backend. Its tasks are the ids with that prefix that node docs/.sw/sw.mjs ready lists at the start, in its order; tasks that become ready later join only when the message asks for them. No prefix matches: that is a question for step 4's message.

  2. Standing answers, settled now and asked never. Each has a default; the user's message overrides a default only where it speaks to that question, and nothing else does: "don't commit" answers commit, not push; "finish them all" sets the scope and answers none; "don't ask me" rules out questions and answers none, so the run still stops when a task stops.

    QuestionDefault
    May plans and proposed splits be approved by the run?yes
    May checks that start a service or need a local stack run?yes, allowed
    May checks that change data run?no, not allowed
    Commit after each task?yes, each done task, message <ID>: <title>
    Push?no
    Go on with other tasks when one stops?no; stop the run

    The answers are said in one line that starts Standing answers: and gives all six. That line is a message to the user, written as given, word for word, in this shape, each default kept where the message gave no answer and the user's answer in its place where it did (commit each done task: no):

    Standing answers: plans and splits approved by the run: yes; checks that start a service or need a local stack: allowed; checks that change data: not allowed; commit each done task: yes, as <ID>: <title>; push: no; when a task stops: stop the run.

    It is the first line of step 4's message, on its own line, before any task is touched. Settling the answers in your reasoning, reporting them in other words, or listing the defaults only in the report does not replace it, since a reader of the session finds the answers by those words; the run file and the report repeat the line.

  3. Check that the run can do what was agreed, without changing anything:

    • node docs/.sw/sw.mjs lint: an error is a point for step 4's message, since the vault is not changed before it.
    • Commits are agreed: run one harmless git command. Refused by the project's settings or the tool: say so in step 4's message, and neither start the run nor work around the refusal.
    • git status: changes in the working tree that are neither a task of this run's (the files its Summary lists, its bookkeeping) nor the run file are a point for step 4's message: whether to leave them or commit them first.
  4. Readiness check, the one place the run asks. Read, for every task in scope: its task file, the pages its "Sources" link, the area guide node docs/.sw/sw.mjs explain <ID> names, and the vault's decision pages on its subject: one call per task, node docs/.sw/sw.mjs search <the task's title, whole>, then, of the hits under docs/wiki/, those whose frontmatter says type: decision; no other search. Read no code and no plan file: the technical points are the planner's and the implementer's, raised mid-run.

    List every point that needs a decision. Before the first task those are only what the task files and the message show without a planner:

    • every Open: line in a task's "Notes";
    • every "Done when" item whose check changes data, deletes a file or pushes, by the item's own words: it names a database, a store or a service beyond the project that the check writes to, a file to delete, or a push. An item whose check starts the project's own server or needs a local stack is not one;
    • every point the message leaves ambiguous: a scope that matches nothing, an answer it half gives;
    • a request, in the message or in a task, that contradicts a decision page;
    • step 3's findings: a lint error, a refused git command, changes in the tree that belong to no task.

    It lists nothing else: a "Done when" item that leaves a design choice open is the planner's or the implementer's to raise. Judge each point by "Points that need a decision" below.

    Then say the readiness message, as text in your output. It is:

    • first line: the Standing answers: line of step 2;
    • then the settled points, one per line: - <ID>: <decision>; settled by <source> (the source as "Points that need a decision" names it);
    • then the questions for the user, one per line, each with the task id and what the run would need; or, with no question, exactly Nothing left to ask: the run starts. on its own line.

    With a question left, the message stands alone and the run waits for the ans

阅读完整来源 ↗