Update to User Intuition

{
  "description": "Use when the user wants to estimate, launch, pause, resume, or stop recruitment for a User Intuition Panel study.",
  "included_files": [
    {
      "relative_path": "references/approval-continuity.md",
      "size_in_bytes": 2304
    }
  ],
  "name": "field-a-panel",
  "skill_md_contents": "---\nname: field-a-panel\ndescription: Use when the user wants to estimate, launch, pause, resume, or stop recruitment for a User Intuition Panel study.\nallowed-tools: Read\n---\n\nWhen the user wants to field a Panel:\n\nApply the shared [approval and workflow continuity policy](references/approval-continuity.md).\n\n1. Call `get_study` and verify `recruiting_method` is `panel` and `provisioning_status` is `provisioned`.\n2. Compare the returned study with any trusted checkpoint. If it matches an already approved plan, carry that approval forward without repeating the review. Otherwise return the complete current `study_plan` with its audience, screeners, concepts, and interview settings, obtain explicit approval, and retain a new checkpoint.\n3. Ask the user to choose one launch country explicitly. Never infer a country from language, location, account data, or a broad region. Each launch fields exactly one country; multi-country work requires separately reviewed country-specific studies or launches.\n4. Read `userintuition://catalog/panel-countries` to verify that the chosen country supports the study language. If the client cannot read MCP resources, use the authenticated `GET /api/public/v1/panel-countries/` endpoint.\n5. If targeting is requested or needs to change, use `customize_study`, complete any questions with the user, then call `get_study`, return the complete revised plan, and obtain approval of the revised version.\n6. If `incident_rate` is below 10 or the audience is unusually specialized, use `submit_feasibility_request` instead of direct launch.\n7. Call the read-only `estimate_panel` with the explicit `country_code` first. Show the resolved country, language, target, incident rate, estimated cost, and timeline (a heuristic). Retain its `estimate_id`.\n8. Add the complete estimate and recruitment settings to the checkpoint. Obtain explicit launch approval through the preview flow below; never infer it from the original request, plan approval, or client permission settings. If the estimate expires or relevant study, launch, balance, or price inputs change, get a fresh estimate and approval.\n9. Call `launch_panel` with the `estimate_id` and the same settings and country to obtain a preview. In clients supporting MCP Apps, the person approves with the App button; `approve_panel_launch` is App-only and must not be called by the model. Without Apps, show the saved plan and complete quote, obtain explicit human confirmation, then call `launch_panel` with the returned `chat_approval_nonce` and `human_confirmed=true`. Never invent a nonce or confirmation. Report what was launched. After an uncertain timeout, retrieve the current study state before considering another launch.\n10. Use `pause_study` to preserve progress and the reward hold, `resume_study` to continue, and `stop_study` to end recruitment and settle or release the hold. Confirm before stopping.\n"
}