/ skills /questions
Skill · Claude Code

questions

Questions you answer on a page, not in the terminal

Use it when Claude has a question, a decision or a confirmation for you, or several piling up, and you would rather answer them all in one pass on a page, at your own pace or from your phone, than hunt for them in chat.

Try it: paste this into Claude Code
Use /proofs:questions to put your open questions for me on a page I can answer.
8 features

1What you see

01

Questions First

Open questions sit at the very top

The questions are the first thing under the top bar, highlighted. Reports, context and settled items come after them, so you never scroll to find what is being asked.

02

Real Buttons, Not Letters

Every question has options you click

Each question has options you select on the page and a notes box for the answer nobody thought to offer. A pinned bar counts what you have answered, and answers save in your browser as you go. You never have to type Q2: C in chat and hope it is understood.

03

The Ask, the Why, a Pick

Each question says why it matters, what each option costs, and Claude's choice

A question states what is being decided, why it matters, and a real trade-off for every option. Claude marks the option it would choose and says why, and keeps defensible options it disagrees with on the list so you can overrule it. Decisions you delegated appear too, as a stated call with an overrule control.

04

See It to Decide It

Visual questions come with drawn mockups

When a question is about where something goes or how it looks, each option is drawn as a mockup at the real width. You choose by looking, not by picturing a description.

05

Answers That Can't Be Misfiled

Every answer carries its question id, the round and the full option text

Each question keeps a short id that never changes, and the copied text opens with the project, stream, round, page link and time. It carries the whole wording of the option you chose, not a letter, and says UNANSWERED plainly for anything you skipped. A late reply to an earlier round still lands on the right question.

06

No Building on Guesses

Claude waits on blocking questions and works around them

Claude stops at a question it truly needs answered, carries on with work that does not depend on it, and does not guess and build on the guess. Answered questions stay on the page as a short record, and things noticed but not done go in a parked list.

07

One Copy Button

Everything you answered, in one paste

Copy my answers gathers every answer and note into one block of text that names the project, so you paste it back once.

08

Where the Page Goes

A private link, a local file, or your Wi-Fi

Your project picks where review pages go: a private claude.ai link, an HTML file that opens in your browser, or that file served on your home Wi-Fi so a phone can open it. Nothing is ever uploaded or tunneled in the Wi-Fi mode, and the server stops when the review ends.