agentleFS
Sign inStart free
SubliminalCodingSubliminalCoding/bilbroswagginz-skills/skills/qwen-project-autopilot/SKILL.md

qwen-project-autopilot

Skill0 starsChanged 47 days agoMITView on GitHub

Local-Qwen 1→done tick loop (token-free). Mechanical checklist form of /project-autopilot for a small local model: take the top ready bead, make the smallest change, verify build→tests→lint, commit or revert, repeat until the bead graph drains, then run qwen-bug-zero and (if speed matters) qwen-perf-max. Stops and asks on any judgment call. Use when you want /project-autopilot's job done on a local model with no API tokens: pushing a scaffolded project toward done.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never widen scope. New ideas that come up → SOMEDAY.md, not new beads, unless the user says so.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

qwen-project-autopilot (local 1→done)

The Qwen-run version of /project-autopilot. No lens diagnosis, no operator psychology: just a tight, gated bead loop. The gates are the safety net.

QWEN LOCAL RULES (full text: ../qwen-forge/references/QWEN-MODE.md)

Requires qwen-forge installed alongside this skill (it holds the shared rules).

  • Builder, not architect. Judgment calls belong to the user.
  • ONE change at a time; build → tests → lint after each; green → commit; red → revert, one retry, else STOP. Never weaken tests.
  • Build ONLY what the Intent needs; extras → SOMEDAY.md.
  • Unclear / judgment / outward → DECISIONS.md + STOP.
  • Local endpoint required: a local OpenAI-compatible endpoint (vLLM, SGLang, llama.cpp or Ollama) serving a capable Qwen-class coding model. ONE model loaded, work SEQUENTIALLY, leave memory headroom on unified-memory machines.

Before the loop

  1. Confirm the baseline is green (build + tests). If red → fixing the baseline is the first task; do that under the loop's gates before anything else.

THE LOOP (repeat)

a. `br ready` → take the TOP task. If none → go to "When the beads drain".
b. Make the SMALLEST change that completes ONLY that task. Touch as little as possible.
c. Run build → tests → lint.
     green → commit (short msg), `br update <id> --status closed`, report one line.
     red   → `git restore` the change; try ONE more fix; still red → STOP and ask.
d. If the task needs a design / naming / scope / taste decision → STOP, write it to
   .autopilot/DECISIONS.md, move to the next ready task.
e. Go to (a).

When the beads drain (br ready empty)

1. Run qwen-bug-zero (find + fix real bugs).
2. If the Intent cares about speed AND features are settled → run qwen-perf-max.
3. Report: "intent features built, bugs swept" + hand to the user for ship (qwen-ship-it).

Rules that keep it on track

  • Never widen scope. New ideas that come up → SOMEDAY.md, not new beads, unless the user says so.
  • Small batches only: one bead, one verify, one commit. The green ratchet is the whole safety system here (there is no smart-model review on a local-only run).

Distilled from /project-autopilot. Its references hold the full lens/routing/operator-moves version for a Claude or human driver.

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.

Check your setup, free