skills/swarm/SKILL.md
Alias for /ro:planner-worker. Multi-agent coding swarm — planner + worker + merger over git worktrees on the Max plan. When the user types /ro:swarm, /swarm, "kick off the swarm", "run the swarm", "swarm coding", or anything matching "swarm + code/PR/PRD", redirect to /ro:planner-worker.
npx skillsauth add RonanCodes/ronan-skills swarmInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This is a thin alias for /ro:planner-worker. Both invocations resolve to the same behaviour.
Use /ro:planner-worker directly — it has the full skill body. /ro:swarm exists so the friendlier word also works.
Use /ro:night-shift if you want a multi-wave indefinite drain across the whole backlog, not just a single planner-worker pass. Night-shift wraps planner-worker with a ranked queue, file-area conflict detection across waves, draft-grilling, parent-PRD auto-slicing, follow-up-issue creation, and an end-of-session nightsheet. It opens with a four-question scope grill so AFK semantics are explicit.
See ~/.claude/plugins/cache/ronan-skills/<v>/skills/planner-worker/SKILL.md for:
--github, --judge-agent, --afk, --workers N, --resume, live status, postmortem.swarm.json config/ro:swarm --prd <name> # same as /ro:planner-worker --prd <name>
/ro:swarm --afk # same as /ro:planner-worker --afk
/ro:swarm --resume # same as /ro:planner-worker --resume
All flags supported by /ro:planner-worker are supported here.
development
--- name: worktree description: Coordinate multiple agents on one repo via a worktree-lock pool, so two agents never clobber each other's working tree. Acquire the first free slot (main, then beta/gamma… worktrees, created on demand), work there on your own branch, release when you've pushed. Use before modifying any repo that might be in use by another agent (factory, dataforce, etc.), or whenever you're told a repo is being worked on. Backed by `ro worktree`. category: development argument-hin
testing
--- name: ship description: Ship a feature branch the local-CI-first way — run the full local gate, push, open a PR, squash-merge, then deploy, without waiting on GitHub Actions. Use when a branch is ready for main and you want it merged and deployed now. Reads CI policy from `ro ci` (default skips remote CI because GitHub Actions billing keeps hitting limits). Sibling to /ro:gh-ship (waits on GitHub checks) and /ro:cf-ship (the deploy half). Triggers on "ship it", "ship this", "merge and deploy
testing
--- name: setup-logging description: Set up (or audit) the observability stack in a TanStack Start + Cloudflare Workers app so it is "diagnosable by default" — structured logging (logtape) with a request context carrying trace_id + userId + tenant/orgId, a trace_id propagated FE→BE→logs→Sentry→PostHog, Cloudflare Workers observability enabled, and Sentry + PostHog wired. Two modes: `setup` (wire it into an app) and `audit` (check an existing app + report gaps). Use when scaffolding a new app, wh
development
Manage credentials INSIDE the active ~/.claude/.env file — read which token/account to use for a given app (Simplicity vs Dataforce vs Ronan-personal), add or update a secret WITHOUT it passing through the chat (an interactive Terminal window prompts for it), and track secrets that were exposed in a transcript so they get rotated. Sibling to /ro:context (which switches WHICH env file is active). Use when the user wants to add an API key/token/secret, asks "which credential do I use for X", needs the env organized/labelled, or a secret was pasted into the chat and should be rotated.