/ask

The decision you cannot settle is not stuck — it is misaddressed. /ask repackages it for the person who can actually answer: enough context to be understood cold, questions sharp enough to be answered in a word where a word suffices, and a discipline for bringing the answers back.

Preconditions

1. There is an unanswered decision — from the conversation, or from a document set's open questions when documents.md pins one.
2. The answer lives with someone else. If the repo or a primary source could answer it, that is /scout; if it is a trade-off to weigh, that is /grill. /ask is for knowledge and authority that is not yours.

Build the questionnaire

The answerer is assumed to have no shared context with this session. Each questionnaire:

• Opens with context: what is being built, in two or three sentences, and why their answer matters — no jargon they have not been given.
• Asks numbered questions, one decision per question, each saying briefly what hangs on it. Where real options exist, list them with a recommended one first; where the answer is free-form, say so and leave room for it.
• Ends with the return instruction: answers come back with who answered and the date — source and date, the same discipline the document family's open questions use.

The questionnaire lands at docs/questions/<slug>.md, ready to hand over.