
Review code, phases, and projects for quality, correctness, and conformance. Supports three modes: task review, phase review, and final review. Each mode runs a conformance-first pass against a per-requirement audit table, followed by a lean quality sweep. Status semantics are scope-aware — task and phase use tiered status (on-track / drift / regression); final uses strict status (met / missing).
Test runner conventions for the foo package. Use when planning tests inside packages/foo/. Mandates the `foo:vitest` npm script as the test command and a `__foo__` test-file suffix.
Continue a project through the orchestration pipeline. Ensures the Orchestrator runs as the primary agent — not as a subagent — so it retains full control of agent sequencing. Use for local, background, or cloud-based execution.
Orchestration system runtime, configuration, and context. All pipeline agents load this skill for system context. The Orchestrator receives pipeline-specific guidance.
Set up a parallel git worktree for a project and launch orchestration execution in it. Use when asked to "run in parallel", "create a worktree", "execute in a worktree", or when launching a project in an isolated branch for parallel development. Handles git worktree creation, branch setup, source control initialization, and opening the worktree in VS Code, Copilot CLI, Claude Code, or a terminal.
Audit the two-doc planning set (Requirements + Master Plan) for codebase accuracy, cross-document cohesion, and explosion-readiness. Two modes: self-review (planner-time) and full audit (reporter subagent; orchestrator dispatches a planner subagent to apply fixes).
Use this skill whenever a task might involve code beyond the current working directory — when you're figuring out where code lives, scoping work that may span multiple repositories, or about to act as if the current repo is the whole system — and whenever the user wants to register, bind, describe, group, or manage repositories and repo-groups. The repo registry is your map of the repos a team works across and how they relate.
Consolidated document-creation skill for Requirements and Master Plan documents. Routes to the appropriate per-document-type workflow based on the invoking agent's action.
Orchestration system runtime, configuration, and context. All pipeline agents load this skill for system context. The Orchestrator receives pipeline-specific guidance.
Configure the orchestration system using a structured questionnaire. Walks through system root, project storage, pipeline limits, gate behavior, and source control settings, then generates orchestration.yml.
Execute a single task end-to-end from a self-contained task-handoff document. Supports `code` (with mandatory RED-GREEN) and `doc` / `config` / `infra` task types, plus handoffs that declare no explicit task type. The handoff is the sole input; no upstream planning docs are read.
Start the planning pipeline in quick mode — same plan/audit/approval ceremony as /rad-plan, but with the quick template, Extra Large task size, and autonomous execution mode hardcoded
Source control operations — commit code or open a PR. All inputs come from the spawn prompt.
Audit the two-doc planning set (Requirements + Master Plan) for codebase accuracy, cross-document cohesion, and explosion-readiness. Two modes: self-review (planner-time) and full audit (reporter subagent; orchestrator dispatches a planner subagent to apply fixes).
Open the post-approval, pre-execution router — delegates to /rad-execute or /rad-execute-parallel
Run the project test suite and report results. Use when executing tests, running unit tests, integration tests, validating code changes, checking test coverage, or verifying acceptance criteria. Provides structured test execution with pass/fail reporting and error details.
This skill can be invoked when the user starts talking about planning or executing a project. Use this skill to run a team of subagents through an automated SDLC process that helps them get work done safely and effectively.
Start the planning pipeline for a new project — produces Requirements + Master Plan
Brainstorm and refine project goals through collaborative ideation. Use when exploring problem spaces, validating concepts, generating UI mockups, building consensus on what to build, creating the project goals and visuals. Trigger when the user talks about brainstorming, goal-setting, idea generation, or early-stage project definition. You can also trigger this skill if they want to generate a mockup, wireframe, architecture or flow diagram, or beautiful html project summary.
Start the planning pipeline for a new project — produces Requirements + Master Plan
Consolidated document-creation skill for Requirements and Master Plan documents. Routes to the appropriate per-document-type workflow based on the invoking agent's action.
Report whether the radorch dashboard UI server is running, and its URL.
Start the radorch dashboard UI as a detached server and report the URL.
Stop the detached radorch dashboard UI server (SIGTERM).
Brainstorm and refine project goals through collaborative ideation. Use when exploring problem spaces, validating concepts, building consensus on what to build, or creating the initial project goals document.
Start the radorch dashboard UI as a detached server and report the URL.
Report whether the radorch dashboard UI server is running, and its URL.
Set up a parallel git worktree for a project and launch orchestration execution in it. Use when asked to "run in parallel", "create a worktree", "execute in a worktree", or when launching a project in an isolated branch for parallel development. Handles git worktree creation, branch setup, source control initialization, and opening the worktree in VS Code, Copilot CLI, Claude Code, or a terminal.
Continue a project through the orchestration pipeline. Ensures the Orchestrator runs as the primary agent — not as a subagent — so it retains full control of agent sequencing. Use for local, background, or cloud-based execution.
Log pipeline execution errors to a structured per-project error log. Use when the pipeline returns success: false, when an agent produces invalid output, or when manual intervention is needed. Appends numbered entries to an append-only error log file.
Stop the detached radorch dashboard UI server (SIGTERM).
Execute a single task end-to-end from a self-contained task-handoff document. Supports `code` (with mandatory RED-GREEN) and `doc` / `config` / `infra` task types, plus handoffs that declare no explicit task type. The handoff is the sole input; no upstream planning docs are read.
Start the planning pipeline for a new project — produces Requirements + Master Plan
Brainstorm and refine project goals through collaborative ideation. Use when exploring problem spaces, validating concepts, building consensus on what to build, or creating the initial project goals document.
Run the project test suite and report results. Use when executing tests, running unit tests, integration tests, validating code changes, checking test coverage, or verifying acceptance criteria. Provides structured test execution with pass/fail reporting and error details.
Report whether the radorch dashboard UI server is running, and its URL.
Execute a single task end-to-end from a self-contained task-handoff document. Supports `code` (with mandatory RED-GREEN) and `doc` / `config` / `infra` task types, plus handoffs that declare no explicit task type. The handoff is the sole input; no upstream planning docs are read.
Source control operations — commit code or open a PR. All inputs come from the spawn prompt.
Open the post-approval, pre-execution router — delegates to /rad-execute or /rad-execute-parallel
Review code, phases, and projects for quality, correctness, and conformance. Supports three modes: task review, phase review, and final review. Each mode runs a conformance-first pass against a per-requirement audit table, followed by a lean quality sweep. Status semantics are scope-aware — task and phase use tiered status (on-track / drift / regression); final uses strict status (met / missing).
Consolidated document-creation skill for Requirements and Master Plan documents. Routes to the appropriate per-document-type workflow based on the invoking agent's action.
Log pipeline execution errors to a structured per-project error log. Use when the pipeline returns success: false, when an agent produces invalid output, or when manual intervention is needed. Appends numbered entries to an append-only error log file.
Start the radorch dashboard UI as a detached server and report the URL.
Stop the detached radorch dashboard UI server (SIGTERM).
Log pipeline execution errors to a structured per-project error log. Use when the pipeline envelope returns ok: false, when an agent produces invalid output, or when manual intervention is needed. Appends numbered entries to an append-only error log file.
Audit the two-doc planning set (Requirements + Master Plan) for codebase accuracy, cross-document cohesion, and explosion-readiness. Two modes: self-review (planner-time) and full audit (reporter subagent; orchestrator dispatches a planner subagent to apply fixes).
Start the radorch dashboard UI as a detached server and report the URL.
Open the post-approval, pre-execution router — delegates to /rad-execute or /rad-execute-parallel
Review code, phases, and projects for quality, correctness, and conformance. Supports three modes: task review, phase review, and final review. Each mode runs a conformance-first pass against a per-requirement audit table, followed by a lean quality sweep. Status semantics are scope-aware — task and phase use tiered status (on-track / drift / regression); final uses strict status (met / missing).
Source control operations — commit code or open a PR. All inputs come from the spawn prompt.
Report whether the radorch dashboard UI server is running, and its URL.
Run the project test suite and report results. Use when executing tests, running unit tests, integration tests, validating code changes, checking test coverage, or verifying acceptance criteria. Provides structured test execution with pass/fail reporting and error details.
Stop the detached radorch dashboard UI server (SIGTERM).
Set up a parallel git worktree for a project and launch orchestration execution in it. Use when asked to "run in parallel", "create a worktree", "execute in a worktree", or when launching a project in an isolated branch for parallel development. Handles git worktree creation, branch setup, source control initialization, and opening the worktree in VS Code, Copilot CLI, Claude Code, or a terminal.
Continue a project through the orchestration pipeline. Ensures the Orchestrator runs as the primary agent — not as a subagent — so it retains full control of agent sequencing. Use for local, background, or cloud-based execution.