brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
critiquing-own-responseReviews 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 independe…
Independent GitHub snapshot · Automated classification · Original documentation governs
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.