discovery-question-form by nexu-io

Decision brief

What it does—and where it fits

When the user's brief is ambiguous, the agent's first turn must surface the smallest possible set of clarifying questions that unblock the rest of the workflow. The questions are rendered as a artifact inline in the originating assistant message. This is assistant text parsed by…

Best for

Not for

Tasks that require unconfirmed production actions or broad system permissions.
Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

Platform	Status	Evidence	What to check
Codex	Not declared	No explicit evidence	Portability before use
Claude Code	Not declared	No explicit evidence	Portability before use
Cursor	Not declared	No explicit evidence	Portability before use
Gemini CLI	Not declared	No explicit evidence	Portability before use

Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource

npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/atoms/discovery-question-form"

Safe inspection promptEditorial

Inspect the Agent Skill "discovery-question-form" from https://github.com/nexu-io/open-design/blob/89d6d4ef21baf80f871595abdf6f7de6e941dd44/plugins/_official/atoms/discovery-question-form/SKILL.md at commit 89d6d4ef21baf80f871595abdf6f7de6e941dd44. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

01
When to fire
Brief is missing audience, target medium, or core intent.
Brief is missing audience, target medium, or core intent.Brief explicitly invites questions ("ask me anything if unclear").The discovery skill or pipeline declares a discovery stage.
02
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.
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.
03
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,
04
Convergence
The discovery atom completes when the next user message contains an answer for every required question. Treat those submitted answers as conversation context and do not ask the same questions again unless later input invalidates an answer.
The discovery atom completes when the next user message contains an answer for every required question. Treat those submitted answers as conversation context and do not ask the same questions again unless later input in…

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial

Signal	Value	Evidence type	Meaning
Quality score	71/100	Computed	Documentation, specificity, maintenance, and trust rules
Repository stars	82,073	Source	Repository attention, not individual Skill quality
Compatibility	0 platforms	Source	Declared in the catalog source record
Usage guide	automated source guide	Editorial	Generated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository: nexu-io/open-design
Skill path: plugins/_official/atoms/discovery-question-form/SKILL.md
Commit: 89d6d4ef21baf80f871595abdf6f7de6e941dd44
License: Apache-2.0
Collected: 2026-07-28
Default branch: main

View the original SKILL.md

Discovery question form

When the user's brief is ambiguous, the agent's first turn must surface the smallest possible set of clarifying questions that unblock the rest of 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>].

When to fire

Brief is missing audience, target medium, or core intent.
Brief explicitly invites questions ("ask me anything if unclear").
The discovery skill or pipeline declares a discovery stage.

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-form id="discovery" title="Quick brief — 30 seconds">
{
  "description": "I'll lock these in before building. Skip what doesn't apply — I'll fill defaults.",
  "questions": [
    {
      "id": "audience",
      "label": "Who's the primary audience?",
      "type": "checkbox",
      "options": ["VC", "Customer", "Internal team"],
      "maxSelections": 2,
      "required": true
    }
  ]
}
</question-form>

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, switch, or direction-cards.
options: required for choice controls; strings are allowed, or objects with localized label and stable value.
allowCustom: leave unset or set to true for finite-choice controls so users can type their own answer instead of accepting only generated options. Set allowCustom: false only when the downstream system needs an exact machine id.
customLabel / customPlaceholder: optional localized copy for that custom answer input.
maxSelections: include this for checkbox controls with a limited selection count.
required: set to true only when the answer is needed before work can continue.

Convergence

The discovery atom completes when the next user message contains an answer for every required question. Treat those submitted answers as conversation context and do not ask the same questions again unless later input invalidates an answer.