Agent skill · writing content · nexu-io
discovery-question-form
Structured clarification form for unresolved material requirements.
Why this skill is useful
Defines a structured protocol for gathering essential information that aids in clarifying project requirements, which the AI may not generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 84,236 stars on the source repository.
What this skill does
Discovery question form This atom defines the <question-form> protocol. It does not decide whether clarification is required. Follow the active skill and core prompt's requirements-clarification policy. When they identify unresolved information that would materially change the design direction, content structure, or delivery format, surface the smallest possible set of questions that unblocks the workflow. The questions are rendered as a <question-form> artifact inline in the originating assistant message. This is assistant text parsed by the host, not a plugin GenUI surface or a native tool call. Submitted answers return as the next user message, beginning with [form answers — <form-id>]. Activation boundary A first turn or new project does not by itself require a form. A discovery pipeline stage only makes this protocol available; declaring or entering the stage does not trigger a form. Missing metadata is not automatically a question. First use the request, conversation, plugin inputs, memory, active skill, and design system. If enough information is available to proceed safely, do not emit a form. If a material blocker remains, ask only for that unresolved information. Emission shape Emit the form as a question-form block whose body is a JSON object with a top-level questions array. Do not emit a bare question object by itself; the renderer only recognizes the wrapped form contract. Question object shape Each entry in the top-level questions array uses: id: stable answer key, for example audience. label: user-facing question copy. type: one of radio, checkbox, select, text, textarea, number, range, date, time, datetime-local, color, url, email, tel, file, or switch. options: required for choice controls; strings are allowed, or objects with localized label and stable value. At most 6-7 options per question; merge near-duplicates instead of listing more. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nexu-io/discovery-question-form