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.
中文简介正在准备中。当前显示原文说明。
Sort contract deviations by the user's playbook priority and route each one to its business owner or counsel.
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Use a completed playbook comparison. Triage is queue order, not legal risk advice.
If the user's playbook names escalation classes, thresholds, owners, or fallbacks, apply them and cite the rule. If it does not, use neutral process labels:
COUNSEL DECISION — a legal position or unsupplied fallback is needed;BUSINESS INPUT — price, scope, service, timing, or owner fact is missing;PLAYBOOK MATCH — the supplied position matches;DOCUMENT GAP — text, definition, exhibit, or version is missing;READY FOR CONFIRMATION — all requested evidence is present, but no approval is implied.Never create high, medium, or low legal-risk grades unless the supplied playbook defines them. Never infer authority from a job title.
Return one row per issue with source section, playbook rule, label, owner, deadline, blocker, supplied fallback, and exact decision. Keep all approvals pending until the named owner records them. Do not accept text, negotiate, or send changes.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示原文说明。