Productivity & Automationlow risk

discovery-question-form

Turn-1 discovery question form for ambiguous briefs.

nexu-io/open-design·plugins/_official/atoms/discovery-question-form/SKILL.md
59/ 100おすすめ度

この Skill を導入

coding agent を選び、プロジェクト用または個人用コマンドをコピーします。

収録 commit に固定
プロジェクトに導入.agents/skills/discovery-question-form
npx skills add https://github.com/nexu-io/open-design/tree/7533db3f4342d09b27368fa5d907ebd3cdb93b75/plugins/_official/atoms/discovery-question-form -a codex -y
個人環境に導入~/.agents/skills/discovery-question-form
npx skills add https://github.com/nexu-io/open-design/tree/7533db3f4342d09b27368fa5d907ebd3cdb93b75/plugins/_official/atoms/discovery-question-form -a codex -g -y
手動配置先.agents/skills/discovery-question-formOfficial docs ↗
プロジェクトに導入.claude/skills/discovery-question-form
npx skills add https://github.com/nexu-io/open-design/tree/7533db3f4342d09b27368fa5d907ebd3cdb93b75/plugins/_official/atoms/discovery-question-form -a claude-code -y
個人環境に導入~/.claude/skills/discovery-question-form
npx skills add https://github.com/nexu-io/open-design/tree/7533db3f4342d09b27368fa5d907ebd3cdb93b75/plugins/_official/atoms/discovery-question-form -a claude-code -g -y
手動配置先.claude/skills/discovery-question-formOfficial docs ↗
プロジェクトに導入.agents/skills/discovery-question-form
npx skills add https://github.com/nexu-io/open-design/tree/7533db3f4342d09b27368fa5d907ebd3cdb93b75/plugins/_official/atoms/discovery-question-form -a github-copilot -y
個人環境に導入~/.copilot/skills/discovery-question-form
npx skills add https://github.com/nexu-io/open-design/tree/7533db3f4342d09b27368fa5d907ebd3cdb93b75/plugins/_official/atoms/discovery-question-form -a github-copilot -g -y
手動配置先.agents/skills/discovery-question-formOfficial docs ↗
プロジェクトに導入.agents/skills/discovery-question-form
npx skills add https://github.com/nexu-io/open-design/tree/7533db3f4342d09b27368fa5d907ebd3cdb93b75/plugins/_official/atoms/discovery-question-form -a cursor -y
個人環境に導入~/.cursor/skills/discovery-question-form
npx skills add https://github.com/nexu-io/open-design/tree/7533db3f4342d09b27368fa5d907ebd3cdb93b75/plugins/_official/atoms/discovery-question-form -a cursor -g -y
手動配置先.agents/skills/discovery-question-formOfficial docs ↗
プロジェクトに導入.agents/skills/discovery-question-form
npx skills add https://github.com/nexu-io/open-design/tree/7533db3f4342d09b27368fa5d907ebd3cdb93b75/plugins/_official/atoms/discovery-question-form -a gemini-cli -y
個人環境に導入~/.gemini/skills/discovery-question-form
npx skills add https://github.com/nexu-io/open-design/tree/7533db3f4342d09b27368fa5d907ebd3cdb93b75/plugins/_official/atoms/discovery-question-form -a gemini-cli -g -y
Native Gemini CLIgemini skills install https://github.com/nexu-io/open-design.git --scope workspace --path plugins/_official/atoms/discovery-question-form
手動配置先.agents/skills/discovery-question-formOfficial docs ↗
⚠ インストールには open-source skills CLI を使用します。実行前にソースと権限を確認してください。
# 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 structured form
(GenUI surface kind: `form`, persist tier: `conversation` so a follow-
up turn doesn't re-ask).

## 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.

```html
<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 every required question has an answer
in `genui_surfaces` for the current conversation. The agent should not
loop back to discovery after that — the same surface id renders cached
on the next turn.