Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
中文简介正在准备中。当前显示原文说明。
Use when the user wants a weekly, monthly, or quarterly business review set up, asks how the business is doing this period, or hands over numbers for a review pack.
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Use this when the user wants a weekly business review (WBR), monthly business review (MBR), or quarterly business review (QBR) set up, asks how the business is doing this period, or hands over numbers for a review.
The cadence (weekly, monthly, quarterly), the KPI set with targets, the numbers from connected sources or pasted exports, and the open actions from the last review.
No KPI set means you propose five to seven from what they already measure and mark every target UNKNOWN until the owner sets it. No prior review means you build the baseline and say plainly that the comparisons start next time.
Say back what you found: the last review date, actions open and overdue, and which KPIs have targets and which do not. Never rebuild a rhythm they already run.
Name the days this review covers and the days it compares against. Never compare a partial period to a full one.
Every line carries FACT, INFERENCE, or UNKNOWN. Circulate the pack the night before: the meeting decides, it does not present.
Numbers (ten minutes), stuck items (ten minutes), decisions (fifteen minutes), actions (five minutes).
The review is exception-based. Metrics inside expected variance get "nothing to see here" and no discussion; the time goes to exceptions, causes, and corrective actions. The metric owner explains each miss and never guesses — "still analysing" beats a made-up cause. A decision without an owner and a date is not a decision.
Write the decision log. Carry open actions forward with new dates. Name the one thing that matters most before the next review. Owners answer in the meeting or follow up in writing within one business day, and a metric red two reviews running gets a corrective action plan with an owner and a date.
Never invent a metric, a target, or a decision. Never email or post the pack anywhere without the owner's yes.
Save dated under reviews, one folder per cadence. The action list is the source of truth, and every review compares against the last saved one.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
中文简介正在准备中。当前显示原文说明。
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
中文简介正在准备中。当前显示原文说明。
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
中文简介正在准备中。当前显示原文说明。
Write ad variants that each test one idea, within platform limits and supported claims.
中文简介正在准备中。当前显示原文说明。
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
中文简介正在准备中。当前显示原文说明。
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
中文简介正在准备中。当前显示原文说明。