Use for creative thinking, or when the user wants many fresh options before choosing: "give me ideas", "brainstorm names", "other ways to do this", "think outside the box". Diverges first, then picks. Skip when one answer is wanted or the task is pure execution.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Defer judgment while generating. Keep generate (Prime, Diverge, Connect) separate from Harvest (pick and plan).
Skip: a single delivered answer with no exploration, audit-only teardown, mechanical execution. If the user is stuck in a rut and wants deliberately odd angles, a provocation-based approach fits better than plain divergence.
2-4 bullets: what would a delightful or surprising success look like? What must not be violated?
Quantity first. Tag each idea F (flexible reuse of something existing), N (novel twist) or W (wild, may be impractical).
Use at least two triggers from: analogy (unrelated domain), constraint flip (remove or add a rule), user fantasy (absurd ideal), time shift (past or future), scale shift (micro or macro).
Combine ideas: A + B -> hybrid concept in a few lines. Fewer than Diverge, never just one unless the brief is tiny.
Worked example: references/example.md.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use for analytical thinking, or when a question needs breaking down and evidence: "why did metric X drop?", "what drives this?", "break this down", "what data do we need?". Builds a tree, hypotheses and evidence, ends with an answer and key uncertainty. Skip for quick verdicts.
The English summary is being prepared. Showing the original description.
Use for critical thinking, or when the user wants a claim, plan or decision checked for weak spots: "is this right?", "what am I missing?", "poke holes", "sanity check", "devil's advocate", "red team this". Skip for execution-only tasks and wording edits.
The English summary is being prepared. Showing the original description.
Use for design thinking, or when a product or service problem needs user understanding before solutions: "what do users really need?", "how might we...", "plan a discovery sprint", "validate this concept". Skip when the spec is frozen or the task is code maintenance.
The English summary is being prepared. Showing the original description.
Use for ethical thinking, or when a plan could harm or unfairly burden people: "should we do this?", "is this fair?", "privacy or bias risk", "who gets hurt?". Maps stakeholders, harms, power and consent. Skip for legal advice, neutral fact lookups and implementation-only work.
The English summary is being prepared. Showing the original description.
Use for Fermi estimation, or when a rough number is needed fast: "roughly how many...", "ballpark the cost", "estimate capacity or market size", "is this even feasible?". Decomposes, uses ranges and sanity-checks. Skip when exact data is available or a precise calculation is wanted.
The English summary is being prepared. Showing the original description.
Use for first principles thinking, or when the user questions an inherited default: "why do we do it this way?", "is this cost really necessary?", "should we copy what competitors do?". Strips analogies and rebuilds from fundamentals. Skip for convention-following checklists.
The English summary is being prepared. Showing the original description.