协作头脑风暴
brainstorming
在实现前澄清需求、探索设计选择,并形成清晰的开发方向。
critiquing-own-response【开发与工程】Reviews the agent's own immediately preceding response as an advisory pass, surfacing assumptions, reasoning gaps, alternatives, and unverified claims. Use ONLY when the user explicitly asks for self-critique, critical thinking, or challenges to the agent's prior answer. Do not use for normal follow-ups, someone else's work, automatic checking, or in…
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Use only when the user explicitly requests critique of the agent's own immediately preceding response and that response exists. Analyze that response only, not the user, unrelated turns, or the whole conversation. This same-model critique shares the original answer's blind spots; it is advisory and never verification or formal review of a high-impact change.
Write entirely in the primary language of the preceding response.
Every finding must cite a specific claim, assumption, or step in the preceding response. Do not manufacture weaknesses; when a category has no real finding, say so briefly.
Core claim:
Important assumptions:
Potential failure modes:
Counterexamples or alternatives:
Evidence still needed:
Revised confidence: higher | unchanged | lower
Close with the single most useful next check when one exists. Do not assign a numeric confidence score or rewrite the answer; the user decides what to act on.