radin-planlisted

# Plan a Backlog Entry Turn one backlog entry into one or more implementation plans, without writing any code. It runs inline in whichever context invokes it. A caller that cannot reach the user says so in its prompt; the branches below marked "non-interactive" are then the defaults, and anything only the user could settle is reported and stops the run. ## Step 1: Resolve the task scope ```bash RADIN_CLI backlog plan-target "<scope id/title/keyword>" ``` It prints `id`/`title`/`task_file`/`plan_file` lines, plus a `facts<TAB><path>` line when the entry carries one, plus one `plan<TAB><path>` line per plan the entry already has. Route on its exit code: - **0**: resolved and unplanned. Use it. - **1**: nothing matches. The task isn't in the backlog yet: classify it into `feat`/`fix`/`chore`/`refactor` (rubric in `skills/radin-record/SKILL.md`), create it without asking, then re-run `plan-target` on the printed id. ```bash RADIN_CLI backlog add <category> "<short title>" <<'EOF' <the task as the caller stated or clearly implied it, and why it matters if not already obvious> EOF ``` - **2**: several entries match; it prints them as `candidate` lines on stderr. Ask which one. - **3**: already planned; the `plan` lines are the existing paths. Show them and ask whether to re-plan (overwrite) or stop. Stop unless confirmed. Non-interactive, for all three: report what `plan-target` printed and stop. The scope came from an existing entry, so no match means b