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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.