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. When the invoking context cannot reach the user (e.g. radin-execute's planning sub-agent), the caller says so, and every question below then takes the non-destructive branch marked "non-interactive". A sub-agent can neither reach the user nor call `AskUserQuestion`, so `/mattpocock-skills:grilling` is interactive-only here: there is no way for it to get an answer. Same for `/mattpocock-skills:research`, which spawns its own agent whose result may never come back within the turn. Each "non-interactive" branch below says what to do instead. ## Step 1: Resolve project namespace All backlog reads/writes go through the shared CLI at `$HOME/.claude/.radin/lib/radin-backlog.sh`. Never hand-edit the backlog's index or task files, and never compute their paths yourself. Get the paths (this also creates the state/plans/reviews/tasks directories): ```bash bash "$HOME/.claude/.radin/lib/radin-backlog.sh" env ``` Read `REPO_ROOT`, `NAMESPACE_DIR`, `BACKLOG_INDEX`, `BACKLOG_TASKS_DIR` from its output. Re-run this line in any later Bash call that uses them. ## Step 2: Resolve the task scope ```bash bash "$HOME/.claude/.radin/lib/radin-backlog.sh" find "<scope id/title/keyword>" ``` It prints one `id<TAB>category<TAB>title<TAB>file` line per match (exact id first, then exact title, else substring on title). - **One match**: us