radin-planlisted

Write a step-by-step implementation plan for one backlog entry, without touching code. Takes a task scope — a title/keyword — instead of the whole backlog. Judges whether the scope is broad enough to split into multiple independent plans, confirms any split with you directly, then writes one plan file per resulting sub-task, reviews it with thermo-nuclear and ponytail-review before handing it off, and appends a `**Plan:**` pointer back to the entry. Use for /radin-plan, "plan this backlog entry", "write a plan for X before we execute it". radin-execute delegates to a planning sub-agent that invokes this skill, non-interactively, for any entry it judges too complex to implement without a plan.
shortcuts/radin · ★ 3 · AI & Automation · score 71

Install: claude install-skill shortcuts/radin

# Plan a Backlog Entry Turn one `BACKLOG.md` entry into one or more concrete implementation plans, without writing any code. This runs inline in whichever context invokes it, so any split judgment or open question surfaces in that conversation. When the invoking context cannot reach the user (e.g. radin-execute's planning sub-agent), the caller says so and this skill's questions resolve to their non-destructive defaults: no split, no overwrite. ## Step 1: Resolve project namespace, locate BACKLOG_FILE All radin state for a project lives inside that project's repo, in `.claude/.radin/` at the repo root (example: repo `/Users/x/proj` → `/Users/x/proj/.claude/.radin/BACKLOG.md`). Do not compute this path yourself — run the shared namespace-resolution script and read `REPO_ROOT`, `NAMESPACE_DIR`, `BACKLOG_FILE` from its output: ```bash bash "$HOME/.claude/radin-lib/radin-namespace.sh" ``` This creates `$NAMESPACE_DIR/state`, `$NAMESPACE_DIR/plans`, and `$NAMESPACE_DIR/reviews`. Re-run this line in any later Bash call before using these variables. ## Step 2: Resolve the task scope Read `$HOME/.claude/radin-lib/radin-prioritization.md`'s "Parsing `$BACKLOG_FILE`" section — you don't need its priority-criteria section, since you're scoping to one entry, not ordering the whole backlog. Match the caller's scope (a title, keyword, or paraphrase) against `### title` entries in `$BACKLOG_FILE`: - **Exactly one match**: use it. - **Multiple candidate matches**: list them and ask