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.
日本語の概要は準備中です。原文の説明を表示しています。
Draft a blameless incident review with an evidence-based timeline, causes, and owned follow-ups.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this after an outage, data issue, or failed release.
Collect alerts, logs, deploys, chat messages, and status updates with timestamps. Build a timeline in one time zone: when it started, when it was noticed, key decisions, when it was fixed, and when it was confirmed fixed. Cite the source for each entry and mark gaps. Add the impact: who was affected, for how long, and what data or money was involved.
Separate the trigger from the conditions that let it cause harm: missing tests, alerts, limits, docs, or rollback. For each, give the evidence and how sure you are. If the cause is not proven, say so and list what would prove it. Describe what systems and steps did, not what people failed to do.
For each follow-up give the action, the problem it prevents, the owner, and a due date. Prefer fixes to systems over reminders to people. Keep the list short enough to finish.
Never name a person as the cause, invent a timeline entry, or claim a root cause without evidence. Do not publish the review or close follow-ups; the incident owner approves it.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
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.
日本語の概要は準備中です。原文の説明を表示しています。