discovery-question-form
Structured clarification form for unresolved material requirements.
Profile →npx skills add nexu-io/open-design --skill discovery-question-form --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 unresolve
- Activation boundary
- Emission shape
- Question object shape
- Convergence
What does the discovery-question-form skill do?
Structured clarification form for unresolved material requirements.
How do I install it?
Run `npx skills add nexu-io/open-design --skill discovery-question-form --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.