rnd-doctorlisted

# R&D Framework: Doctor Run environment readiness checks and report status for each category. ## 1. CLI Tools For each of the following tools, run `which <tool>` to check availability, then capture the version: - `bash` — run `bash --version | head -1` - `jq` — run `jq --version` - `git` — run `git --version` - `duckdb` — run `duckdb --version` (optional — warn but do not fail if missing) ## 2. Hook Scripts Read the hooks configuration using the Read tool: ``` Read: "${CLAUDE_PLUGIN_ROOT}/hooks/hooks.json" ``` Extract all hook script paths referenced in the JSON (the `command` or `script` fields). For each script path, check that it exists and is executable: ```bash ls -la "${CLAUDE_PLUGIN_ROOT}/hooks/" ``` Report how many hook scripts are present and executable out of the total referenced. ## 3. RND Artifact Directory Run rnd-dir.sh to determine or create the artifact directory: ```bash RND_DIR=$("${CLAUDE_PLUGIN_ROOT}/lib/rnd-dir.sh" -c) ``` Check if the command succeeded (exit code 0) and if `$RND_DIR` is a writable directory. Also check for an active session: ```bash BASE_DIR=$("${CLAUDE_PLUGIN_ROOT}/lib/rnd-dir.sh" --base) CURRENT_SESSION_FILE="${BASE_DIR}/.current-session" ``` Report whether `$RND_DIR` is writable and whether an active session exists. ## 4. Plugin Registration Look for the local marketplace registry file. Check common paths: - `"${CLAUDE_PLUGIN_ROOT}/../../.claude-plugin/marketplace.json"` (repo root) - `~/.claude/marketplace.json` R