> ## Documentation Index
> Fetch the complete documentation index at: https://docs.userintuition.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Create study from brief

> Use when the user wants to create a User Intuition interview study from a brief, goal, problem, or research idea.

Use when the user wants to create a User Intuition interview study from a brief, goal, problem, or research idea.

[Fetch raw SKILL.md](https://raw.githubusercontent.com/user-intuition/skills/1f5880347343099a9cbf38e4832d9a0b7338b85e/plugins/user-intuition-research/skills/create-study-from-brief/SKILL.md) · [Source](https://github.com/user-intuition/skills/blob/1f5880347343099a9cbf38e4832d9a0b7338b85e/plugins/user-intuition-research/skills/create-study-from-brief/SKILL.md) · [All skills](/skills/library)

Requires an authenticated [User Intuition MCP connection](/mcp-server/quickstart). Install the raw file as `create-study-from-brief/SKILL.md` inside your agent client's supported skills directory. The raw file is the installable artifact; this page is its documentation wrapper.

SHA-256: `b5030ecba240ae70b030ee9792afcbfc23df6917f06905ee0da729152bc3e75d`

## Instructions

```markdown theme={null}
---
name: create-study-from-brief
description: Use when the user wants to create a User Intuition interview study from a brief, goal, problem, or research idea.
---

When the user asks to create a study:

1. Ask Panel versus BYOP when unstated. Set `recruiting_method` to `panel` when User Intuition should recruit, or `byop` when the user supplies participants. Never guess.
2. Keep the name to 40 characters. Unless the user requests an override, omit `interview_format`, `language`, and `voice` so `create_study` applies the current defaults: a voice interview in English with Elliot. If the user requests another mode or language, use `list_available_modes` or `list_available_languages` for discovery. The public voice override is `male` (Elliot) or `female` (Clara); provider-specific IDs from `list_voices` are not accepted. Never supply `voice` for chat.
3. Use `list_study_types` only when the user needs help choosing a type. Do not draft a plan from its prompts; the backend applies the selected type's current Customize Plan instructions.
4. Call `create_study` with ordinary metadata only.
5. Call `customize_study` with the user's natural-language brief, including their audience, screening needs, and requested concept links or images. Do not construct a plan, targeting attributes, screeners, duration, or concept objects in the MCP host.
6. If `response_type` is `question`, relay the question to the user and call `customize_study` again with their answer. Never decide for them.
7. When customization completes, call `get_study`. Return the complete persisted study plan in a readable form together with its audience, screeners, concepts, interview settings, and `provisioning_status`. Do not replace it with a summary or dashboard link.
8. Ask the user to approve that exact plan version or request revisions. Send revisions through `customize_study`, fetch the study again, and repeat the complete review. Approval of an earlier version does not cover a revised plan.
9. Verify `provisioning_status` is `provisioned` before fielding. Return the study ID and, when present, both `dashboard_url` and `study_link`; label `study_link` as the live participant interview link, not a preview. Never create BYOP participants or launch a paid Panel without current-plan approval. Panel launch also requires a dry-run and separate approval of its complete estimate.
```