radin-recordlisted

Log feedback, bugs, follow-ups, or ideas raised mid-session as structured BACKLOG.md entries, so they survive past the conversation. Use for /radin-record, "log this to BACKLOG.md", "add as follow-up/bug/idea", "record what we just found", "note this for later", "add findings to backlog". Triggers even on vague asks ("add the findings") — scan the whole session, not just the literal text.
shortcuts/radin · ★ 3 · AI & Automation · score 71

Install: claude install-skill shortcuts/radin

# Record to Backlog Turn feedback, bugs, follow-ups, or ideas raised during a live session into structured entries in `BACKLOG.md`, so they survive past the conversation that surfaced them. This is the capture step for everything that isn't a code-review finding — things a human said, not things a diff revealed. `radin-review` logs code-review findings instead. `radin-plan` and `radin-execute` consume the backlog afterward. ## 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" ``` Re-run this line in any later Bash call before using these variables. ## Step 2: Decide what to log The user's instruction after `/radin-record` decides scope: - **Specific** (names a particular thing — "add the auth timeout bug", "log the caching idea we discussed"): log exactly that item. Don't go digging for other candidates the user didn't point at. - **Generic** ("add the findings", "log what we discussed", bare `/radin-record` with no argument): scan the whole session so far for anything a reasonable person would call a bug, follow-up, idea, or piece of feedback. Include things the user state