crossthink
When every option on the table is a variation of one route or waits on the same sign-in, approval, person or dependency, list the options that frame already gives, then map working mechanisms from five or more distant domains onto the problem and report the ones the first list lacked, each with where it breaks. Use when work is stuck inside one frame, when the user asks how another field or industry would solve it, or asks for an analogy that actually transfers. Not for re-reading a decision at a larger scale (macrothink), listing options when no single frame is stuck, or checking claims (fact
Try your first task
A source-grounded starter task has not been verified for this skill yet.
SKILL.md
name: crossthinkdescription: "When every option on the table is a variation of one route or waits on the same sign-in, approval, person or dependency, list the options that frame already gives, then map working mechanisms from five or more distant domains onto the problem and report the ones the first list lacked, each with where it breaks. Use when work is stuck inside one frame, when the user asks how another field or industry would solve it, or asks for an analogy that actually transfers. Not for re-reading a decision at a larger scale (macrothink), listing options when no single frame is stuck, or checking claims (factchk)."List what the problem's own frame already offers, then borrow working mechanisms from distant domains and keep only the ones that list lacked.
Goal
A problem stuck in one frame keeps producing variations of one route. A mechanism that already works in another domain can open a route the frame hides, but only when the transfer is operational: the source mechanism is real, the target mapping says who or what does which step here, and the breaks-where names the condition in this setting under which it fails. The run returns the new mechanisms with their breaks-where, or says honestly that the mapping found none.
The mapping does not replace direct generation. On the problems it was tried on, direct generation found more usable mechanisms, and the mapping still found ones direct generation missed, most of them about keeping the work safe while the blocker stands (reconciliation, staging against a stand-in, escalation, findings kept as text).
Workflow
- State the problem and its frame. Write the goal, the hard constraints, the stated unknowns and the frame that narrows the options now: the route every current option takes and the step it waits on, if any. Keep the problem's facts; drop the session's preferred answer.
- List the frame's own options first. Write the distinct mechanisms the problem already yields directly, one line each: how it works here and what it needs. This list is the baseline the mapping is judged against, so write it before choosing any domain.
- Map distant domains until five rows are accepted. Pick domains far from the problem's field (logistics, biology, law, finance, film, games, hardware, cognitive science, real estate, or others). For each, fill three cells:
- source mechanism: an operation or causal process that actually works in that domain, stated as what happens, not as a slogan;
- target mapping: the concrete option it yields here, saying who or what performs which step and what it requires;
- breaks-where: the specific condition in this setting under which the transfer fails, and how to handle it when it can be handled. "May not work" or a cost alone is not a condition.
- Reject what does not transfer. A row with an empty cell, a mapping that only renames words with no operation behind it, and a source mechanism you cannot state as a working operation (reject it as unverified; this pass does not check sources) go to a rejected list with the reason.
- Fold and subtract. Fold rows that share one working operation into one mechanism; a different domain, vendor, tool, parameter or wording does not make a new one. Move every mechanism already on the step 2 list to the rejected list with the reason
already direct: <its step 2 line>. What remains is the result. - Report. Lead with the new mechanisms, each with its domain, target mapping and breaks-where: first those that remove the blocker, then those that limit its damage while it stands. Name the cheapest observation that would confirm or break the first one. Close with the rejected list. Zero new mechanisms is a valid result: say so and keep the step 2 list as the answer.
Rules
- Direct options are written first and never replaced by the mapping; the mapping is judged only by what it adds.
- A rejected row is kept with its reason, never deleted.
- Never invent a fact about a source domain. Checking a claim against sources belongs to
factchk. - Re-reading the same decision at a larger scale, purpose or horizon is a vertical read and belongs to
macrothink; this skill reads sideways, across domains. - Read-only and advisory: it proposes options and changes nothing, and choosing among them stays with the main work.
Verification
Before finishing, confirm:
- The frame and the step 2 list were written before any domain was mapped.
- At least five rows were accepted. Each has a source mechanism, a target mapping and a concrete breaks-where.
- No reported mechanism is already on the step 2 list, and rows sharing one operation were folded.
- Every rejected row, the already-direct ones included, is listed with its reason.
- The report names one next observation, or states that the mapping added nothing.