RAD_framework: Command for Claude Code

/rad-review

Self-review the rad/[feature] work branch before requesting architect review. Catches problems early — better to find them now than in the architect's review of the deliver PR.

Input

$ARGUMENTS (optional): specific files to review. If empty, reviews all changes on the current rad/[feature] branch since it diverged from the default branch.

BASE=$(scripts/get-default-branch.sh)
git diff "$BASE"...HEAD --name-only

---

Process

Step 1: Load context

• Read AGENTS.md for project conventions and constraints (or CLAUDE.md if the project has no AGENTS.md)
• Read the plan file for this work branch:

  BASE=$(scripts/get-default-branch.sh)
  FEATURE=$(git branch --show-current | sed 's#^rad/##')
  PLAN=".agents/plans/$FEATURE.md"
  

• Read the execution log:

  LOG=$(ls .agents/logs/$FEATURE-*.md 2>/dev/null | tail -1)
  

Step 1b: Review digest

node harness/cli.js digest "$FEATURE"

Run the read-only review digest and include its full output verbatim in the report's ### Digest section. It ranks where to look first (scope violations, approval not intact, un-waived then waived high-risk paths, self-protected paths, deficit forecast, finding recurrence, run evidence) and shows unavailable inputs explicitly. The digest is advisory only — it informs the review and never changes its pass/fail by itself.

If it exits non-zero (2 = usage error or unreadable plan, 1 = malformed event log), record the exit code and its stderr in the ### Digest section and continue the review — a digest failure is reported, never a stop.

Step 2: Scope check

scripts/check-scope.sh "$PLAN" "rad/$FEATURE" "$BASE"

The script outputs each changed file as in-scope or out-of-scope. Include its full output in the review report. Any out-of-scope files are HIGH priority.

Step 2b: Lint advisories

scripts/lint-plan.sh "$PLAN"

Run the plan linter against the plan under review and include its full output in the review report. These are advisory only — they surface plan-quality warnings for the architect's attention but do not gate the review or block architect review. This is separate from the Step 2 scope check.