RAD_framework: Command for Claude Code

rad-adopt

Convert a pre-existing issue into a RAD plan. Use this for work that existed before the RAD framework was introduced.

Input

The input ($ARGUMENTS) can be:

• A GitHub/GitLab issue URL: https://github.com/org/repo/issues/42
• An issue number: #42 or 42
• A free-form description: "Fix the login timeout not resetting on activity"

If empty, ask for the issue reference or description before proceeding.

--override-disposition "<reason>" may accompany the input to proceed past a research artifact's cited non-actionable disposition (see Step 2b). The override and its reason are recorded in the plan header.

--playbook <kind>/<slug>[@<version>] may accompany the input to start from a pinned playbook in .agents/playbooks/ (see Step 3b). A bare ref pins the playbook's current version.

---

Process

Step 1: Determine role and available agents

Read the role and scope config from .rad/config.yml (see docs/configuration.md):

node harness/cli.js config get roles.developers   # also roles.designers, roles.architect
node harness/cli.js config get agent_scope_map    # one { agent, type, reads, roles } row per line

From that output, find:

• The current user's role (architect, developer, or designer)
• Which agents are available for this role (rows whose roles include it)

Only call agents available to your role. Flag out-of-scope dependencies in the plan rather than working around them.

Step 2: Fetch issue context

If $ARGUMENTS is a URL or issue number:

# GitHub
gh issue view [number-or-url] --json title,body,labels,comments,assignees,url

# GitLab
glab issue view [number-or-url] --output json

Extract:

• Title
• Body / description
• Labels
• Comments (summarize if long — keep to ≤10 lines)
• Issue URL (for Adopted-From: field)

If the CLI is unavailable or the fetch fails, prompt the user to paste the issue content directly and use that as the description.