Back to Hermes Agent

Routing Heuristics

optional-skills/creative/creative-ideation/references/heuristics.md

2026.7.15.0 KB
Original Source

Routing Heuristics

Decision tree for picking a method. Read top to bottom; first match wins.

Phase signals — what stage is the user in?

SignalMethod
Blank page, no domainconstraint dispatch (full-prompt-library.md)
Has a domain, no projectroute by domain (next section)
Has one idea, want variationsmethods/scamper.md
Need many ideas fastmethods/volume-generation.md
Idea too safemethods/lateral-provocations.md
Many ideas, need to choosemethods/premortem-and-inversion.md
Have idea, want to sharpenmethods/creative-discipline.md (Tharp's spine)
Stuck mid-projectmethods/oblique-strategies.md
"Is this any good?"methods/premortem-and-inversion.md + methods/compression-progress.md

Domain signals

DomainMethod
Fiction with formal interestmethods/oulipo.md
Narrative with story shapemethods/story-skeletons.md
Essay / non-fictionmethods/defamiliarization.md + methods/compression-progress.md
Poetrymethods/oulipo.md or methods/chance-and-remix.md
Lyrics / songwritingmethods/oblique-strategies.md + methods/chance-and-remix.md
Music / soundmethods/oblique-strategies.md (origin domain)
Visual art / sculpture / installationmethods/oblique-strategies.md, methods/creative-discipline.md (LeWitt)
Performance / theatermethods/defamiliarization.md (Brecht)
Site-specificmethods/derive-and-mapping.md
Engineering inventionmethods/triz-principles.md
Software architecturemethods/pattern-languages.md
Algorithm / data structuremethods/polya.md + methods/first-principles.md
Civic / policymethods/leverage-points.md
Org designmethods/leverage-points.md + methods/pattern-languages.md
Research / picking a questionmethods/compression-progress.md
Attacking a known problemmethods/polya.md + methods/first-principles.md
Product strategy / why-does-this-existmethods/jobs-to-be-done.md
New venture from scratchfull-prompt-library.md "solve your own itch" + methods/jobs-to-be-done.md
Career / what to studymethods/derive-and-mapping.md + methods/compression-progress.md
Habit / disciplinemethods/creative-discipline.md

Mood / tone signals

User wantsMethod
Beautiful / elegantmethods/compression-progress.md
Weird / strangemethods/pataphysics.md, methods/chance-and-remix.md
Useful / practicalmethods/triz-principles.md, methods/jobs-to-be-done.md, "solve your own itch"
Fun / playfulmethods/oulipo.md, methods/oblique-strategies.md
Serious / rigorousmethods/polya.md, methods/first-principles.md, methods/compression-progress.md
Personal / intimatemethods/creative-discipline.md, methods/derive-and-mapping.md
Political / interventionmethods/leverage-points.md, methods/chance-and-remix.md (détournement)
Critical / subversivemethods/defamiliarization.md, methods/pataphysics.md

When to stack methods (rare)

Most invocations: one method. Stack only when:

  • Domain method + provocation. OuLiPo + de Bono PO when the constraint alone produces predictable output.
  • Generation + selection. Crazy 8s → premortem on top three.
  • Drift + pattern. Dérive then affinity-map.
  • Theoretical + practical. TRIZ identifies the contradiction → biomimicry supplies the analog.

Anti-pattern: stacking three+ methods. Becomes process performance rather than ideation.

Edge cases

  • Wild prompt that fits no path → constraint dispatch with the closest matching constraint.
  • User asks for method recommendation, not ideas → surface 2–3 candidate methods, ask which to apply. Don't silently default.
  • High-slop terrain ("AI ideas", "startup ideas", "habit tracker") → force methods/lateral-provocations.md or methods/pataphysics.md over the obvious method. Refuse the first 5 ideas, not 3.
  • Same question asked again → switch methods. Variation in method = variation in idea distribution.
  • User frustrated / says everything is bad → don't keep generating. methods/creative-discipline.md (Cleese open mode, Tharp scratching). Sometimes the right move is to stop ideating.
  • User wants to be talked out of starting → premortem. Inversion. Sometimes the right answer is "don't do this".

Anti-patterns

  1. Defaulting to constraint dispatch when the user has rich domain signals. Read first.
  2. SCAMPER without a base idea. SCAMPER amplifies; doesn't generate from nothing.
  3. TRIZ on artistic or social problems. Its parameters are physical/engineering.
  4. Leverage points on a single-creator project. Overkill — Meadows is for multi-actor systems.
  5. Reaching for the most exotic method to seem sophisticated. Constraint dispatch is right most of the time.
  6. Stacking methods to compensate for not picking well. Bad choice + bad choice ≠ better choice.
  7. Generating finished work when the user asked for direction. Wait until they pick.