RAD_framework: Command for Claude Code

/rad-deliver

Execute an approved plan wave by wave. Each wave is delegated to a sub-agent with only the files it needs. Main context stays lean — it orchestrates and logs, never accumulates task implementation detail.

Under the Lane B model the work has lived on its rad/[feature] branch since /rad-plan — that branch carries the plan, the approval, and now the code. There is no separate deliver branch, and the deliver PR is the only PR.

Input

$ARGUMENTS must be the path to a plan file:

/rad-deliver .agents/plans/email-confirmation.md

If empty, list available approved plans (reading branch tips):

scripts/rad-status.sh 2>/dev/null | grep approved || echo "No approved plans found."

---

Process

Step 1: Resolve and validate the work branch

Read the plan file's Branch: header and validate it. Never cut a new branch — a plan missing the Branch: field (or carrying an old plan//deliver/ name) was created before the Lane B workflow:

PLAN_FILE="$ARGUMENTS"
WORK_BRANCH=$(grep -E '^Branch:' "$PLAN_FILE" | head -1 | awk '{print $2}')

if [[ ! "$WORK_BRANCH" =~ ^rad/[a-z0-9][a-z0-9-]*$ ]]; then
  echo "✗ Invalid or missing Branch field: '${WORK_BRANCH:-<missing>}' (expected rad/<feature>)."
  echo "  This plan predates the branch-at-creation workflow. Recreate it with /rad-plan, or add the Branch field manually."
  exit 1
fi

Step 2: Verify the plan is approved

The gate evaluates the appended approved event over the feature's event log (.agents/state/<feature>/events.jsonl) — the event log is the approval authority. The plan-doc Status: header is display-only and is not consulted by the gate. The check still runs against the plan's own branch tip:

scripts/check-plan-approved.sh "$WORK_BRANCH"

If not approved:

✗ Cannot execute: plan is not yet approved.

Plan:   [plan file]
Branch: [work branch]

The architect must run /rad-approve [feature-name] before execution can begin.

Stop. Do not proceed.