customer-insight

Use when the final customer journey map, CJM, or touchpoint-based journey table must be produced from a completed persona, product or service, or a `handoff_to_customer_journey_mapper` block, especially when the user asks for 顧客旅程地圖, CJM, final journey table, or wants prior persona/framing work turned into the finished map. Also trigger when the user asks for 情緒分數, 情緒曲線, 加減分原因, sparkline, or wants emotion scoring added to an existing CJM.

Use when building a persona, customer profile, or journey-prep brief from a product, audience clue, or usage context, especially for persona、人物誌、顧客輪廓、使用者輪廓、目標客群、5W1H、接觸點盤點、顧客旅程前置分析、或需要簡報化的顧客研究摘要。

Use when research, analysis, evaluation, diagnosis, discovery, insight, or study-design tasks require deciding between qualitative, quantitative, or mixed-methods approaches, especially when the user does not specify a method or the work needs both measurement and explanation.

Run a product-analysis focused revealed-preference logistic conjoint workflow (product specs + reviews/transactions, stacked binary choice, logistic estimation) — from attribute design through business insights (importance, willingness-to-pay, optimal product configuration, pricing and cost-benefit). Use this skill when the goal is to analyze products and infer multi-attribute preferences from observed market behavior, not a generic survey-only conjoint setup.

Use when customer reviews, support tickets, app store feedback, or other review-like text must be converted into STP analysis through a review scoring workflow upstream and statistical scripts downstream.