What problem does it solve? After planning a project with /rad-plan, teams need a controlled way to actually run the execution pipeline — handling fresh launches, in-place runs, and resumed sessions without manually re-deriving branches, worktrees, or settings. This Skill removes that guesswork by delegating all classification to the rad-orchestration CLI and only running the human confirmation beats it flags. ## Core Features & Use Cases - Run-mode resolution: Calls execute resolve to classify the run as launch, in-place, resume, or unknown, then acts only on the flags the CLI returns. - Guided human beats: Asks exactly the questions the resolver flags — launch flavor (Claude Code, Copilot CLI, VS Code), workspace selection, clone binding, auto-commit, and auto-PR — in a single combined prompt. - Session recording and pipeline handoff: Saves session metadata before signaling pipeline start, then continues driving the DAG through the rad-orchestration skill. - Use Case: A developer finishes planning a feature with /rad-plan, invokes /rad-execute, picks a fresh worktree workspace and Copilot CLI launch flavor, and the pipeline starts with commit and PR behavior already sealed. ## Quick Start Ask the assistant to run /rad-execute for your planned project name and answer the confirmation questions it presents.
