メニュー
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.
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.
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 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-create-plans |
| description | 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. |
| user-invocable | false |
A consolidated skill for authoring planning documents. Routing is by an explicit mode the caller declares; each workflow is self-contained.
requirements — author the project Requirements document. Followed
inline by the main agent during or after a /rad-brainstorm collaboration
(the brainstorm context carries straight into authoring).master-plan — author the project Master Plan. Followed
inline by the main agent, handed the spawn_master_plan action by the
pipeline.Write requirement IDs (R{n}) into the code, tests, or comment bodies of the
tasks you author. IDs are planning scaffolding — they live only on the ### R{n}
headings in the Requirements doc, never inside a task's body, code, test, or
comment text.
| Mode | Follow |
|---|---|
requirements | references/requirements/workflow.md |
master-plan | references/master-plan/workflow.md |
The caller declares the mode it is invoking under:
/rad-brainstorm, authors the Requirements
doc inline under requirements.spawn_master_plan action by the pipeline,
authors the Master Plan inline under master-plan.