Build a weighted decision matrix to evaluate options. Use when the user says "decision matrix", "compare options", "weighted scoring", "which option should we choose", "evaluate alternatives", "Wiegers priority matrix", "force field analysis", "decision table", "trade-off analysis", "option comparison" - even if they don't explicitly say "decision matrix".
中文简介正在准备中。当前显示原文说明。
Write a Functional Requirements Document. Use when the user says "write an FRD", "functional requirements", "system requirements", "SRS", "what should the system do", "document the functional specs", "software requirements specification", "detailed requirements for engineering", "functional spec" - even if they don't explicitly say "FRD".
中文简介正在准备中。当前显示原文说明。
Identify gaps between current and desired state. Use when the user says "gap analysis", "what's missing", "current vs future state", "where are the gaps", "capability gap", "maturity assessment", "fit-gap analysis", "what needs to change", "compare current to target", "readiness assessment" - even if they don't explicitly say "gap analysis".
中文简介正在准备中。当前显示原文说明。
Assess business impact of a proposed change. Use when the user says "impact assessment", "impact analysis", "what will this change affect", "change impact", "who is impacted", "ripple effects", "downstream impact", "impact mapping", "what breaks if we change this", "readiness for change" - even if they don't explicitly say "impact assessment".
中文简介正在准备中。当前显示原文说明。
Facilitate structured requirements gathering. Use when the user says "gather requirements", "elicitation session", "stakeholder interview", "requirements workshop", "what do the users need", "discover requirements", "trawl for requirements", "understand the business need", "conduct interviews", or needs to systematically extract requirements from stakeholders - even if they don't explicitly say "elicitation".
中文简介正在准备中。当前显示原文说明。
Find the root cause of a problem, not just symptoms. Use when the user says "root cause", "why does this keep happening", "5 whys", "fishbone diagram", "cause analysis", "problem investigation", "defect analysis", "incident analysis", "A3 problem solving", "what's causing this", "ishikawa" - even if they don't explicitly say "root cause analysis".
中文简介正在准备中。当前显示原文说明。
Map stakeholders by influence, interest, and communication needs. Use when the user says "stakeholder analysis", "stakeholder map", "power interest grid", "who are the stakeholders", "RACI matrix", "stakeholder engagement plan", "who needs to be involved", "communication plan for stakeholders", "influence mapping" - even if they don't explicitly say "stakeholder map".
中文简介正在准备中。当前显示原文说明。
Write structured use cases with main and alternate flows. Use when the user says "write a use case", "document the user flow", "use case diagram", "actor goal list", "main success scenario", "fully dressed use case", "what does the user do step by step", "system behavior for this feature", "interaction flow" - even if they don't explicitly say "use case".
中文简介正在准备中。当前显示原文说明。
Write a consulting engagement proposal. Use when a consultant says "write me a proposal", "draft a proposal for [your client]", "I need to send a proposal", "how do I structure a proposal", "client wants a SOW", "write a statement of work", "I need to propose a project", or "help me price and scope this engagement". Also trigger when someone describes a client conversation that ended with "send me something in writing".
中文简介正在准备中。当前显示原文说明。
Define the scope, success criteria, roles, and boundaries for a consulting engagement. Use when a consultant says "help me scope this engagement", "I need to define what's in and out", "the client keeps adding things", "scope is getting fuzzy", "we need a contracting conversation", "I'm not sure what we actually agreed to", "help me set boundaries with a client", or "what should be in a kickoff". Also trigger when describing an engagement that feels like it is expanding without agreement, or when starting a new client relationship and preparing the initial contract or SOW.
中文简介正在准备中。当前显示原文说明。
Write an executive summary using the Pyramid Principle SCQA structure. Use when a consultant says "write an executive summary", "I need a one-pager for the exec", "how do I open this report", "write me the intro for this deck", "draft the cover memo", "I need to frame the findings", "executive doesn't have time to read the full report", "help me write the storyline", or "write the situation-complication-answer". Also trigger when someone has findings or recommendations and needs to communicate them top-down to a time-constrained audience.
中文简介正在准备中。当前显示原文说明。
Structure a consulting findings presentation using the Pyramid Principle storyline. Use when a consultant says "help me structure my presentation", "I have findings and need to present them", "how do I structure the deck", "build me the storyline", "help me tell the story of the findings", "I have data but no narrative", "client presentation is next week", "how do I present recommendations to the steering committee", or "the deck needs a through-line". Also trigger when someone has completed analysis and needs to communicate findings and recommendations to senior client stakeholders in a structured, persuasive format.
中文简介正在准备中。当前显示原文说明。
Decompose a business problem MECE using an issue tree, generate hypotheses, and prioritize branches for investigation. Use when a consultant says "help me structure this problem", "I need to break down this issue", "build me an issue tree", "I don't know where to start on this problem", "help me frame the problem", "what are the hypotheses here", "we need to prioritize our analysis", or "the client problem is too broad". Also trigger when describing a complex or ambiguous business problem that needs systematic decomposition before analysis begins, or when an engagement is starting and a workplan needs to be structured from a problem statement.
中文简介正在准备中。当前显示原文说明。
Write a structured client status report for a consulting engagement. Use when a consultant says "write my weekly status update", "I need to send a status report", "draft the client update", "what should be in the weekly report", "client wants a progress update", "help me write the RAG status", "I need to report on blockers", "end of week update to the client", or "help me communicate what's stuck". Also trigger when someone needs to communicate engagement progress, surface blockers to the client, or flag decisions that need to be made by the sponsor.
中文简介正在准备中。当前显示原文说明。
Analyze customer health signals, identify churn risk flags, and generate an intervention playbook. Use when user says "churn risk", "customer at risk", "red account", "at-risk customer", "health score dropped", "renewal at risk", "customer going dark", "cancel risk", or "what's wrong with this account" - even if they don't say "churn" explicitly. Applies to CSMs triaging accounts or building proactive retention workflows.
中文简介正在准备中。当前显示原文说明。
De-escalate a customer crisis using a structured acknowledge-triage-DRI-cadence-resolution framework. Use when user says "customer escalation", "angry customer", "exec escalation", "customer threatening to leave", "fire drill", "critical customer issue", "customer is livid", "customer complaint escalated", or "how do I handle this" about a tense situation - even if they don't say "escalation" explicitly. Applies to CSMs and CS managers managing high-stakes customer crises.
中文简介正在准备中。当前显示原文说明。
Identify expansion signals and structure upsell or cross-sell conversations using land-and-expand and Net Revenue Retention principles. Use when user says "upsell", "expansion", "cross-sell", "grow the account", "increase ARR", "find expansion opportunities", "NRR improvement", "upgrade conversation", "add-on", "renewal and expand", or "land and expand" - even if they don't say "expansion discovery" explicitly. Applies to CSMs managing account growth or CS teams building expansion playbooks.
中文简介正在准备中。当前显示原文说明。
Build a customer health scorecard across usage, engagement, adoption, NPS, support load, and financial risk. Use when user says "health score", "customer health", "build a scorecard", "how healthy is this account", "customer scoring model", "green yellow red", "health dashboard", or "account health framework" - even if they don't say "scorecard" explicitly. Applies to CSMs building account health models or CS leaders standardizing health tracking across the team.
中文简介正在准备中。当前显示原文说明。
Design a 100-day customer onboarding plan with phase gates based on Never Lose a Customer Again by Joey Coleman. Use when user says "onboarding plan", "new customer onboarding", "customer kickoff", "first 90 days", "activation plan", "customer launch plan", "new customer journey", or "implementation plan" - even if they don't say "100 days" explicitly. Applies to CSMs designing structured onboarding programs that move customers from signed contract to full adoption.
中文简介正在准备中。当前显示原文说明。
Build a structured Quarterly Business Review deck for a customer account. Use when user says "QBR", "quarterly business review", "prep my QBR", "build the deck", "renewal prep", "executive check-in", "90-day review", or "customer business review" - even if they don't use the acronym. Applies to CSMs preparing for executive-level customer meetings focused on value delivered, health, and next quarter alignment.
中文简介正在准备中。当前显示原文说明。
Write an ETL operational runbook. Use when the user says "ETL runbook", "pipeline runbook", "data job runbook", "how to operate this ETL", "on-call guide for data pipelines", "what to do when the data job fails", "pipeline troubleshooting guide", "data ops runbook", or needs to document how to operate, monitor, and recover a data pipeline or ETL job - even if they don't explicitly say "runbook".
中文简介正在准备中。当前显示原文说明。
Write a data pipeline design document. Use when the user says "pipeline design doc", "document this pipeline", "pipeline architecture doc", "data flow document", "how does this pipeline work", "design doc for ETL", "pipeline spec", or needs to capture the architecture, data flow, and operational details of a data pipeline - even if they don't explicitly say "design doc".
中文简介正在准备中。当前显示原文说明。
Write a data schema specification document. Use when the user says "schema spec", "document this schema", "schema design doc", "data model spec", "table spec", "field definitions", "schema contract", "data dictionary", "define these fields", or needs to formally document a database schema, event schema, or API payload schema - even if they don't explicitly say "schema spec".
中文简介正在准备中。当前显示原文说明。
Run exploratory data analysis on a dataset and produce a structured report. Use when the user says "explore this dataset", "EDA on X", "analyze this data", "what's in this dataset", "summarize this data", "first look at the data", "understand this dataset before modeling", "data quality check", "describe this dataframe", or wants to understand a new dataset before building models or dashboards.
中文简介正在准备中。当前显示原文说明。