From claude-rudder
Capture a follow-up task that surfaced mid-flow but shouldn't distract from the current focus. Appends to `<repo>/planning/leftover-tasks.md` (auto-scaffolds if missing). Use when the user says "park this", "leftover task", "note this for later", "follow-up but not now", "don't let me forget about X", or when Claude and the user mutually agree to defer something rather than context-switch.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin claude-rudderThis skill uses the workspace's default tool permissions.
Append a deferred follow-up to the lightweight planning structure without leaving the current task. Designed to take seconds — minimal interruption, maximum recall later.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Append a deferred follow-up to the lightweight planning structure without leaving the current task. Designed to take seconds — minimal interruption, maximum recall later.
If the follow-up is in-scope of the current task, just add it to the working TODO. This skill is for things that would otherwise derail the session.
repo_root=$(git rev-parse --show-toplevel 2>/dev/null) || repo_root="$PWD"
target="$repo_root/planning/leftover-tasks.md"
If target doesn't exist, run scaffold-planning first (silently — don't pause to ask). After scaffolding, target will exist with a header and template.
If cwd is not in a git repo and the user didn't specify a target, ask:
Capture this as a leftover task in: (1) cwd's
planning/leftover-tasks.md, (2) global$CLAUDE_USER_DATA/claude-rudder/leftover-tasks.md, or (3) somewhere else?
Default to (1) but confirm.
In one short prompt or by inferring from context, get:
small, medium, large, or unknown. Default unknown if user doesn't sayDon't over-interrogate. If the user has only given a one-liner, fill the rest with reasonable inferences and a Context: <propose> that they can confirm or revise.
Build the entry:
## 2026-04-27 18:53 — Refactor auth middleware to drop legacy session-token path
- **Surfaced during:** debugging the new login flow in src/auth/login.ts
- **Why deferred:** would derail the current bug fix — pure tech-debt
- **Context:** see `src/auth/legacy-session.ts`; new flow already in place but old code still referenced. ~200 LOC removal.
- **Estimated scope:** medium
- **Status:** open
Append to target after the existing <!-- new entries appended below --> marker (or just at end of file). Each entry is separated from the next by a single blank line.
Use ISO-8601 minute resolution for the timestamp, in the local timezone. Example: 2026-04-27 18:53 (no seconds, no timezone — keep it readable; the marker is the absent timezone).
Print one line:
✓ Captured: "Refactor auth middleware..." → planning/leftover-tasks.md (3 open total)
The "(N open total)" tally is helpful — it lets the user see the parking lot is filling up and consider running start-leftover soon.
Don't elaborate. Don't summarise the captured task back at length. The whole point is minimum interruption — get back to what we were doing.
If the user provides multiple follow-ups in one go ("park these three: …, …, …"), handle as a loop:
start-leftover — picks up an entry from this file in a fresh sessionscaffold-planning — creates the file and surrounding structurelog-blocker — for things blocking progress (different category)leftover-aggregator agent — proactively scans conversation for missed defer-moments