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 names a direction, a bet, a vision, or a strategy doc, or asks whether to build a thing at all: the three-whys narrative, evidence graded for and against, the business case with a kill line, and the ask.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this when the user names a direction, a bet, a vision, or a strategy doc, or asks whether to build something at all. The output is a strategy doc that drives one decision, not a document that ends in observations.
The bet or direction, who the user is, what is known so far, and the decision the doc has to drive. No numbers means you size with bands and mark every assumption. If the user cannot name the user, say so and do not write the doc yet.
The dated strategy doc: narrative, graded evidence for and against, substitutes, business case with the kill line, and the ask. Take one round of edits, then save it. Offer to turn the first bet into roadmap items — only on the owner's yes.
Thin evidence means a smaller bet and a louder UNKNOWN, not a confident doc. Name the one piece of evidence that would move a claim up a grade, and who would get it. Never invent a market size, a customer, or a win, and never frame an E-grade belief as evidence.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
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.
日本語の概要は準備中です。原文の説明を表示しています。