How do I install the Coordinator Yolo skill?

Run npx skillmds@latest add andvl1/coordinator-yolo in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Coordinator Yolo safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Coordinator Yolo?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Coordinator Yolo free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Coordinator Yolo?

andvl1 (@andvl1) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Coordinator Yolo by andvl1 — Agent Skill

Name: Coordinator Yolo
Author: andvl1

Coordinator Yolo

Autonomous night mode — user is away. Each /loop tick runs coordinator-yolo for ONE task through the regular /team, inside an isolated yolo branch. Never main, never push. Triggers on "/team-yolo", "yolo mode", "run autonomously overnight". Explicit opt-in; stop with coordinator-yolo-stop.

andvl1 d519d37 2.6 KB Updated Sep 17, 2026

File contents

coordinator-yolo

Autonomous night mode. The user is away — the coordinator moves the project forward toward the long-term vision, but in a sandbox: one task per tick via the regular /team, all changes only in a yolo branch off main, no questions.

Not a whole-feature swallow. The coordinator is an overseer, not the doer. Per tick it takes one task and runs the normal /team on it. Cadence is the /loop interval.

Safe to run alongside an active /team feature. The tick first checks whether the project is actively moving on something else (active branch / active state / open PR / unfinished e2e) and only picks a task in a quiet area — so it catches the moments when an agent stops (checkpoint wait, needs-human, crash, abandoned sub-task) instead of racing the in-flight work.

Argument

$ARGUMENTS — pulse interval (10m, 15m, 30m). Empty → 10m.

Steps

Read the methodology in agents/coordinator-yolo.md.
Preconditions (else do NOT start): coordinator/<slug>/vision.md exists (else /pulse / vision-bootstrap first); git status --short clean; build + test known.

Cut the branch off main:

SLUG=$(basename "$(git rev-parse --show-toplevel 2>/dev/null || pwd)")
TS=$(date +%Y%m%d-%H%M)
git checkout main && git checkout -b "yolo/$SLUG-$TS"

Run the interval loop — each tick = one task via coordinator-yolo, which runs the regular /team:

/loop <interval> Task(subagent_type: "coordinator-yolo",
  prompt: "one autonomous yolo tick in yolo/<slug>-<ts>: pick the single highest-leverage
           task from vision/backlog, run the regular /team on it (autonomous), validate
           build+tests, commit to the yolo branch or roll back")

Tell the user: started, branch name, interval, how to stop (/coordinator-yolo-stop).

Rails (hard)

yolo branch off main only. Never: main, merge, push, force, prod-deploy, destructive git.
One task per tick; each validated (build+test) before an atomic commit; red → rollback + log.
No AskUserQuestion — decisions autonomous, logged with "why".
Respect vision.md anti-scope. DoD still applies (each task runs the normal /team).

Stop

/coordinator-yolo-stop — halts the loop and produces the report.

---name: coordinator-yolodescription: Autonomous night mode — user is away. Each /loop tick runs coordinator-yolo for ONE task through the regular /team, inside an isolated yolo branch. Never main, never push. Triggers on "/team-yolo", "yolo mode", "run autonomously overnight". Explicit opt-in; stop with coordinator-yolo-stop.---# coordinator-yolo**Autonomous night mode.** The user is away — the coordinator moves the project forward toward thelong-term vision, but in a sandbox: one task per tick via the regular `/team`, all changes only in ayolo branch off main, no questions.**Not a whole-feature swallow.** The coordinator is an overseer, not the doer. Per tick it takes**one** task and runs the normal `/team` on it. Cadence is the `/loop` interval.**Safe to run alongside an active `/team` feature.** The tick first checks whether the project isactively moving on something else (active branch / active state / open PR / unfinished e2e) andonly picks a task in a quiet area — so it catches the moments when an agent stops (checkpoint wait,needs-human, crash, abandoned sub-task) instead of racing the in-flight work.## Argument`$ARGUMENTS` — pulse interval (`10m`, `15m`, `30m`). Empty → `10m`.## Steps1. Read the methodology in `agents/coordinator-yolo.md`.2. **Preconditions** (else do NOT start): `coordinator/<slug>/vision.md` exists (else `/pulse` / vision-bootstrap first); `git status --short` clean; build + test known.3. **Cut the branch off main:** ```bash SLUG=$(basename "$(git rev-parse --show-toplevel 2>/dev/null || pwd)") TS=$(date +%Y%m%d-%H%M) git checkout main && git checkout -b "yolo/$SLUG-$TS" ```4. **Run the interval loop** — each tick = one task via `coordinator-yolo`, which runs the regular `/team`: ``` /loop <interval> Task(subagent_type: "coordinator-yolo", prompt: "one autonomous yolo tick in yolo/<slug>-<ts>: pick the single highest-leverage task from vision/backlog, run the regular /team on it (autonomous), validate build+tests, commit to the yolo branch or roll back") ```5. Tell the user: started, branch name, interval, how to stop (`/coordinator-yolo-stop`).## Rails (hard)- yolo branch off main only. Never: main, merge, push, force, prod-deploy, destructive git.- One task per tick; each validated (build+test) before an atomic commit; red → rollback + log.- No `AskUserQuestion` — decisions autonomous, logged with "why".- Respect `vision.md` anti-scope. DoD still applies (each task runs the normal `/team`).## Stop`/coordinator-yolo-stop` — halts the loop and produces the report.

Frequently asked questions