Individual skill

discovery-question-form

0upvotes

Structured clarification form for unresolved material requirements.

plugins/_official/atoms/discovery-question-form/SKILL.md

Read pinned source

Source commit e7a18df64d0e5e1161903e93bb5a302229dbeb96

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 106,823
Repository last updated: Nov 9, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

ai-design Repository topic
byok Repository topic
design-systems Repository topic
claude-design Repository topic
hermes-agent Repository topic
agent-skills Repository topic
desktop-app Repository topic
figma-alternative Repository topic
prototyping Repository topic
ui-generator Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 6,017 bytes
open-design.jsonasset · 828 bytes

Read excerpt


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