Ask a few focused questions to define a goal, checkable finish conditions, evidence of completion, and constraints. Use when the user wants help clarifying what success means before doing the work.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Ask the user a few concise questions to clearly define:
Use what is already known from the conversation. Ask only about meaningful gaps, in small batches, and follow up where answers are still ambiguous. Suggest concrete finish conditions and evidence when that makes answering easier.
After the answers are clear, summarize the goal, finish conditions, evidence for each condition, and constraints in a short brief. Make any remaining assumptions explicit.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Investigate why a defect or insufficiency was introduced and accepted by tracing code, pull requests, task context, and accessible development sessions. Use for second-order learning after a fix, blameless root-cause analysis, or preventing a recurring class of engineering mistakes.
日本語の概要は準備中です。原文の説明を表示しています。
Design, refine, implement, or review application UI and user journeys with minimal controls, clear actions, shared components, realistic prototypes, and polished behavior. Use for product screens, forms, onboarding, navigation, settings, and chat/task interfaces; not backend-only work or general graphic design.
日本語の概要は準備中です。原文の説明を表示しています。
Structure any communication artifact — documents, reports, plans, issue comments, PR descriptions, emails, presentations, slides, charts, and dashboards — using Jean-luc Doumont's "Trees, Maps, and Theorems" method. Use whenever the goal is to get a message across to a busy audience, when asked to improve clarity or structure of writing or slides, or when a deliverable will be judged by whether readers act on it, not just read it.
日本語の概要は準備中です。原文の説明を表示しています。