next-promptlisted

# Generate Continuation Prompt Produce a self-contained prompt a fresh Claude Code session can paste in to continue this work. The job is to **transfer what this session knows** — what was done, what was decided, what to watch out for, and what's next. The new session can read git, CLAUDE.md, and the codebase itself; don't spend the prompt re-deriving those. Spend it on the knowledge that would otherwise be lost when this session ends. ## Gather - The next task: use `<user-arguments>` if given; otherwise infer from this session's work, the Current State / plan notes, or TODO/status sections. If nothing's obvious, ask. - Absolute paths of the docs the next session should read (CLAUDE.md, specs, plan files). If your team keeps prior context in a knowledge vault or wiki, point the next session at the specific notes that matter - the service note, the project note, the decision record - never at the vault root. A pointer the next session has to go searching from is a pointer it will skip. - The session-specific knowledge: what got done, decisions made, gotchas hit, and any in-flight state that isn't written down anywhere yet. ## Emit Print the prompt in one fenced block so the user can see it, then **launch it as a new background agent** so it shows up in the Claude Code Agents screen (not the clipboard): 1. Write the prompt body verbatim to a temp file via a quoted heredoc (`<<'PROMPT'` — preserves backticks/quotes/newlines; never `echo`): ```bash f="$