콘텐츠로 이동

Conversational

You will produce a conversational UI spec for the surface described in $ARGUMENTS.

Input

Parse $ARGUMENTS. Expect: - Surface (e.g., "customer support chatbot", "voice search feature", "AI onboarding chat", "Bixby Capsule for ride hailing", "KakaoTalk channel bot"). - Optionally: type, modality, audience, brand voice, backend.

If ambiguous, ask one clarifying question — but only one. Otherwise apply reasonable defaults and proceed.

Steps

  1. Pick the type (voice / chatbot / AI / live agent / hybrid) and modality (voice-only / voice+visual / text-only / multimodal).

  2. Apply the conversational-ui-designer playbook:

  3. Define persona (honorific level for Korean, formality, warmth).
  4. Spec turn-taking model.
  5. Document top intents OR LLM system prompt summary.
  6. Map key conversation flows.
  7. Plan error recovery.
  8. Plan human handoff.
  9. Apply Korean compliance if applicable (개인정보보호법, 정보통신망법, 자본시장법).

  10. Plan accessibility.

  11. Output using the structure in PLAYBOOK.md step 11.

Done when

  • Type + modality + use case + audience explicit.
  • Persona (honorific level, formality, warmth, user addressing).
  • Turn-taking model.
  • Top intents / system prompt summary.
  • Conversation flows mapped.
  • Error recovery for each failure type.
  • Human handoff path.
  • Korean compliance addressed if applicable.
  • Accessibility addressed.
  • Required UI components listed.
  • "Don't" catches 2-3 misuses.
  • Verification phase from PLAYBOOK.md passes.