Menú
Start the radorch dashboard UI dev server (next dev, live reload) from the source repo, auto-building the @rad-orchestration/* lib dist first.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use this skill once you are aligned on a project and ready to start. Typically this is invoked directly by the user after /rad-brainstorm has completed and the Requirements doc is approved. It is the reference for how to run the planning pipeline and author the Master Plan.
Drive the release flow locally — context, version reconcile, build, validate, CHANGELOG, commit, sync plugins to the marketplace, and tag/push (which triggers the CI npm publish + GitHub Release), then a post-release dev bump.
Use this skill if you are a main agent, coder agent and have this skill assigned. It is the reference for how to perform source-control operations like creating commits, opening pull requests, and creating or cleaning up worktrees for a project.
Use this skill if you're a main agent orchestrator executing a rad-orchestration project. It is the reference for how to run the pipeline, signal events, execute actions, and manage the overall flow of a project. Typically, you are guided to using this skill when /rad-execute is invoked, but you may read it if you need to refresh your memory due to compaction during an execution.
Rebuild the standard installer and reinstall one harness (claude, copilot-vscode, or copilot-cli) locally — build the rad-orc tarball, stop the UI, uninstall then reinstall the harness, restart the UI. Use to dogfood canonical harness-files/ agent and skill edits into ~/.claude or ~/.copilot.
Use this skill if you are a main agent who is helping to author planning documents (Requirements or Master Plan). This is triggered by the pipeline or by a brainstorm handoff. It is the reference for how to author planning documents in the rad-orc workflow.
| name | rad-ui-dev |
| description | Start the radorch dashboard UI dev server (next dev, live reload) from the source repo, auto-building the @rad-orchestration/* lib dist first. |
| user-invocable | true |
Launch the dashboard dev build with Fast Refresh. Unlike rad-ui-start (which runs the
production standalone server from ~/.radorc/ui via the installed CLI), this is a
source-repo / dogfood operation: it runs next dev against the working tree, so the repo
and its node_modules must be present (it is not meant for an installed end-user plugin).
Run the launcher in the background from the rad-orc-source repo. Always run npm install at the
repo root first — a fresh git worktree has no node_modules (worktrees don't share the parent
checkout's install), so without it the lib dist build fails immediately with 'tsc' is not recognized before next dev can start. npm install is idempotent: once deps are present it's a
fast no-op (up to date), so running it every time is safe.
npm install # at the rad-orc-source root — ensures workspace deps exist (fresh worktrees have none)
cd ui && npm run dev:live # auto-wires RADORCH_CLI_PATH + auto-builds the @rad-orchestration/* lib dist, then next dev
For live library editing (rebuild a lib and restart next dev whenever its lib/*/src
changes), use the watch variant instead:
npm run dev:live:watch # dev:live + --watch-libs
dev:live builds the UI's @rad-orchestration/* workspace deps (dist/) before starting
next dev, so the data path is never stale on launch — this is the whole point of the skill;
no manual cd lib/<pkg> && npm run build step is needed. (Add --skip-libs to skip that
startup build for a fast pure-UI session.) If the local CLI bundle (cli/dist/bin/radorch.js)
is missing it prints a warning and continues — read-only surfaces still work, but gate actions
and the compose Preview 500 until you build the CLI (cd cli && npm run build).
After launching, wait for Ready / Local: in the output, then report the URL —
http://localhost:3000 — to the user. Surface any lib build failure verbatim (the launcher
exits non-zero rather than starting next dev on a broken dist).
To stop it, terminate the dev process tree holding port 3000 (it is a plain next dev
process — rad-ui-stop does not apply; that targets the production radorch ui server
tracked by a PID file).