discovery-question-form

Generate structured clarification forms to resolve material design requirements during discovery phases.

93.2k|10.8k|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/nexu-io/open-design --skill discovery-question-form
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discovery-question-form
Source: https://github.com/nexu-io/open-design/tree/main/plugins/_official/atoms/discovery-question-form
Command: npx skills add https://github.com/nexu-io/open-design --skill discovery-question-form

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the ambiguity in design briefs by providing a standardized, machine-readable way to request missing information from users, preventing design rework and misaligned expectations.

Core Features & Use Cases

  • Structured Clarification: Emits a <question-form> artifact that the host parses to collect specific, required user input.
  • Flexible Input Types: Supports a wide range of input controls including radio, checkbox, select, text, and range sliders.
  • Use Case: When a user requests a new landing page but fails to specify the target audience or primary goal, this Skill generates a quick form to capture those missing details before the design process begins.

Quick Start

Use the discovery-question-form to ask the user for their primary audience and project goals before proceeding with the design.

Frequently Asked Questions about discovery-question-form

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trigger a discovery question form?

The discovery-question-form is triggered when the assistant identifies a material blocker in the design brief that requires user clarification. You emit the form as a <question-form> block containing a JSON object with your specific questions.

What input types are supported in the question form?

The form supports a variety of input types including radio, checkbox, select, text, textarea, number, range, date, time, color, url, email, tel, file, switch, and direction-cards.

Can I make questions mandatory for the user?

Yes, you can set the 'required' field to true within the question object. This ensures the user must provide an answer before the workflow can continue.

How are user answers returned to the assistant?

Submitted answers are returned as the next user message, starting with the prefix '[form answers — <form-id>]'. The assistant then parses these answers to update the conversation context.

When should I avoid using a discovery form?

Do not use a form if enough information is already available to proceed safely. Avoid using forms for minor details that do not materially change the design direction or delivery format.