[FEATURE] /stb: live list of open questions with stable IDs (answer "Q3 yes, Q7 later")

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When building or debugging a feature, one request spawns 3–5 questions from Claude, and each answer triggers more. Closed questions can go through AskUserQuestion, but open questions (free-text decisions, "which folder?", "should X also do Y?") are written in prose and get buried in the scrollback.

To come back to them I have to scroll, highlight, quote, or retype "#1 blah blah". Questions get silently dropped: Claude then proceeds on an assumption (wasted work) or waits for an answer nobody noticed was needed (stalled work). This happens daily in long feature-building sessions.

Proposed Solution

A built-in /stb (standby) command that shows a live checklist of the conversation's unanswered questions:

• Each question gets a stable ID (Q1, Q2, …) that never changes, even several messages later.
• I can answer out of order in plain text: "Q3 yes, Q7 later, Q2 use the NAS share". Claude maps answers to IDs.
• The list updates itself: answered → checked off; deferred ("later") → stays open, marked as parked; new questions from Claude are appended with the next ID.
• Covers both open (free-text) and closed questions, regardless of whether they were asked in prose or through AskUserQuestion.
• Ideally visible as a side panel in the desktop app Code tab (like the task list), with click-to-jump to where the question was asked. /stb alone in the CLI would already be a big win.

Alternative Solutions

• Manual convention: asking Claude to number every question and end each reply with an "Open questions" block. Works until the list drifts or Claude renumbers.
• Many public repos solve this by hand with skills that keep an "Open questions" section in plans/specs/handover files (e.g. notgeorge/how-its-done, LippInc/save-before-compact). Everyone rebuilds the same workaround.
• A local skill that re-reads the conversation and lists open questions. Possible, but it can't render a persistent panel or keep IDs stable across compaction.

Related (closed as stale, not as rejected): #79078 (side panel for open questions; this request adds stable IDs and out-of-order answers) and #55971 (numbered topics).

Priority

High - Significant impact on productivity

Feature Category

Interactive mode (TUI)

Use Case Example

1. I ask Claude to add an export feature to an internal PHP tool.
2. Claude replies with 5 questions: Q1 format? Q2 which users? Q3 include archived rows? Q4 file naming? Q5 where to save?
3. I answer "Q1 CSV, Q3 no", and ask a side question about the database.
4. Claude answers it and asks Q6 and Q7.
5. I type /stb and see: Q2, Q4, Q5, Q6, Q7 still open. I answer "Q2 managers only, Q5 the NAS share, Q7 later".
6. Nothing falls through the cracks, and I never have to quote or retype a question.

Picture: a meeting action-item list. Items can be closed in any order without forgetting one.

Additional Context

Environment: Claude desktop app (Code tab), Windows, daily use for real business automation (Python/PHP tools, databases, SharePoint, NAS).