メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
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.
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.
Use this still if you are a coder agent and have this skill assigned. It is the reference for how to perform a coding task.
| name | rad-dogfood-harness |
| description | 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. |
| user-invocable | true |
Rebuild the standard installer and reinstall one harness so your canonical harness-files/ agent and skill edits land in ~/.claude (or ~/.copilot).
AskUserQuestion: claude / copilot-vscode / copilot-cli. Save the choice as {harness}.
node harness-installers/standard/build-scripts/build.js
npm pack --workspace harness-installers/standard
Both commands run from the repo root — do not cd into the installer directory, or the repo-root-relative {tarballPath} below will break in the later npx steps. npm pack --workspace writes rad-orc-{version}.tgz into the repo root. Read {version} from harness-installers/standard/package.json and capture the absolute path of the tarball as {tarballPath}. Stop and report if either command exits non-zero.
Invoke /rad-ui-stop.
npx file:{tarballPath} uninstall --yes --harness {harness}
npx file:{tarballPath} --yes --harness {harness}
Expected: exit 0 and a post-install summary listing {harness}.
Invoke /rad-ui-start and report the data.url.
file: prefix is required on npm 11+; uninstall must come before the flags.claude from inside a Claude session briefly removes ~/.claude/skills/rad-* during uninstall — keep the step order (/rad-ui-stop before uninstall, /rad-ui-start after reinstall).npm install once at the repo root first so the build can resolve esbuild and next.