rnd-planlisted

# R&D Framework: Plan Only ## Task Input If `$ARGUMENTS` is empty (user ran `/rnd-framework:rnd-plan` with no task description): 1. **Quick codebase scan.** Run a few fast commands to gather context: `git log --oneline -10`, check for TODO/FIXME comments, look at recent changes. 2. **Ask with `AskUserQuestion`.** Present 2-4 concrete task suggestions based on what you found, plus always include a generic "Describe a different task" option. 3. **If the user picks a suggestion**, use it as the task description and continue below. **If they type a custom task**, use that instead. **Never fall back to plain text** to ask what to work on. `AskUserQuestion` is mandatory at every decision point, including this one. If `$ARGUMENTS` is provided, skip this section and proceed directly. ## Plan Run ONLY the planning phase for: $ARGUMENTS 1. Determine the RND artifacts directory and create its structure: ```bash RND_DIR=$("${CLAUDE_PLUGIN_ROOT}/lib/rnd-dir.sh" -c) ``` 2. Invoke `rnd-framework:rnd-decomposition` to load decomposition discipline. 3. **Discover environment and infrastructure.** Run a structured checklist scan: - Package manager (Glob for package.json, Cargo.toml, etc.) - Test framework (Grep for test runner configs, count existing tests, identify run commands) - CI config (Read .github/workflows/ or equivalent) - External services (Grep for https:// URLs in source) - Environment variables (Read .env.example, Grep for process.env/ENV refer