
Good Thinking
- 349 installs
- 133 repo stars
- Updated February 24, 2026
- jwynia/agent-skills
good-thinking is a Claude Code skill that improves agent reasoning before implementation by clarifying goals, surfacing assumptions, and structuring tradeoff decisions for developers who need coherent plans before writin
About
good-thinking is a skill from jwynia/agent-skills that front-loads structured reasoning into agent sessions before any build work starts. It prompts clarification of goals, explicit assumption listing, tradeoff analysis, and decision framing so later implementation steps stay aligned with intent. Developers invoke it when a feature request is ambiguous, when multiple architectural paths exist, or when an agent risks jumping straight to code without validating constraints. The skill acts as a cognitive checkpoint rather than a code generator, producing clearer problem statements and decision records that downstream skills can execute against. Use good-thinking at session start for complex features, refactors with competing approaches, or any task where unstated assumptions could derail delivery.
- Structured reasoning prompts
- Assumption surfacing
- Tradeoff framing
- Goal clarification
- Decision hygiene
Good Thinking by the numbers
- 349 all-time installs (skills.sh)
- +4 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #2,135 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jwynia/agent-skills --skill good-thinkingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 349 |
|---|---|
| repo stars | ★ 133 |
| Last updated | February 24, 2026 |
| Repository | jwynia/agent-skills ↗ |
How do you improve agent reasoning before coding?
Improve agent reasoning before building: clarify goals, surface assumptions, weigh tradeoffs, and structure decisions so downstream implementation stays coherent.
Who is it for?
Developers starting ambiguous features who want structured reasoning and explicit tradeoffs before any code is written.
Skip if: Straightforward bug fixes with a single obvious patch and no architectural or product ambiguity.
When should I use this skill?
The user presents an ambiguous feature, competing approaches, or unstated assumptions and needs structured reasoning before implementation.
What you get
Clarified goals, documented assumptions, tradeoff analysis, and structured decision frames guiding implementation.
Files
Core Principle
Good thinking is an active achievement, not a default state. Operations without orientation produce sophisticated wrong answers; orientation without operations produces good intentions with no traction.
Two structurally different things must work together: operations (cognitive verbs that transform representations) and orientations (what the operations are in service of). Every thinking failure can be located as an operation failing, an orientation captured, or — most commonly and most dangerously — operations functioning well in service of the wrong orientation.
The orientation that produces good thinking is process-sovereignty: the process of inquiry is what's committed to; conclusions are what move. This skill diagnoses when that orientation has been captured and which operations need adjustment.
When to Use This Skill
Use when:
- Reasoning feels stuck or circular
- A conclusion feels defended rather than discovered
- Confidence is high but evidence is thin
- You need to audit whether thinking is serving inquiry or serving comfort
- Analysis is becoming more elaborate without becoming more accurate
- Someone (self or user) is explaining away evidence rather than integrating it
- The same approach keeps being applied despite poor results
The Two Entity Types
Operations
Seven operations that transform representations. They work in complementary pairs — polarities to oscillate between, not choices. The skill is in the oscillation. Operations are powerful, general-purpose, and completely agnostic about what they serve. The same operations that produce genuine insight also produce sophisticated self-deception.
Orientations
What the operations are in service of. Orientations don't process information — they provide the reference point that makes self-correction meaningful. Defined by what is held fixed while everything else moves.
Process-sovereignty (the target orientation): inquiry is responsive to evidence and environment. Conclusions move when evidence demands it. Methods adapt when the situation requires it. What stays fixed is the meta-commitment to responsiveness itself.
Non-inquiry orientations (what capture looks like):
- Conclusion-preservation: A conclusion is fixed; the process bends to defend it
- Authority-preservation: Being the authority is fixed; conclusions and process both flex to maintain status
- Threat-reduction: Discomfort is the driver; complexity misread as danger; resolution sought for relief
- Completion-seeking: Producing an answer that sounds good is the goal, not accuracy
The Seven Operations
Decouple / Re-couple
Detach a representation from its current binding — belief, identity, context, emotional charge — so it can be examined freely. Then reattach it to reality.
Use when: Working within an unexamined frame. A problem comes pre-framed. Response to an idea is entangled with who proposed it. Need to consider a possibility that conflicts with current position.
Failure modes: Fusion (cannot separate idea from framing because the framing feels like "just how it is"). Dissociation (decoupling without re-coupling — pure detachment that never grounds back in reality).
Differentiate / Integrate
Differentiate: Increase resolution. What appears to be one thing is actually several things. Find the joints. Integrate: Construct connections between separate elements. Build wholes from parts. Find common structure.
Use when: The differentiate-then-integrate rhythm is the engine of productive thinking. Quality of synthesis depends on quality of prior analysis.
Failure modes: Under-differentiation (complex treated as simple). Over-differentiation (analysis paralysis). Premature integration (forcing coherence before adequate distinction). Failed integration ("and also" thinking — listing without connecting).
Match
Detect structural correspondence. "This is like that." Also anomaly detection: "This should be like that but isn't."
Use when: Working a problem — what other problems share its structure? Evaluating an approach — where has it succeeded or failed? Something surprises — what did the model predict instead?
Failure modes: False matching (apophenia). Surface matching (visible features rather than deep structure). Restricted match space — the most dangerous: you can only match against categories your current frame contains. Premature frame-commitment narrows match space invisibly.
Monitor / Interrupt
Evaluate whether the current cognitive process is working and intervene when it isn't. The self-corrective operation. Primary interface between operations and orientations — checks whether operations are serving the active orientation.
Use when: Always. Monitor is continuous. When confidence is high and stakes matter, Monitor is most needed, not least.
Critical warning — Monitor co-option: Under non-inquiry orientations, Monitor doesn't just fail to correct — it actively defends the wrong orientation by suppressing operations that would threaten the fixed point. The self-corrective machinery becomes self-protective machinery. This is invisible from inside.
Hold / Resolve
Hold: Actively maintain multiple elements in unresolved tension against pressure to collapse into resolution. Preserves representational flexibility — keeps the recognition space open. Resolve: Close, commit, decide.
Use when: Hold when the problem is genuinely ambiguous, multiple framings seem viable, pressure to resolve comes from discomfort rather than adequacy of analysis. Resolve when sufficient differentiation and matching have occurred.
Failure modes: Premature resolution (narrows what the system can recognize, not just what it searches for). Perpetual hold (indefinite holding without integrating — avoidance disguised as open-mindedness).
Compress / Expand
Compress: Create a lower-dimensional representation preserving essential structure while discarding detail. Build a map from a territory. Expand: Return to the source, recover what was discarded, check whether the compression preserved what it needed to.
Failure modes: Compression that imposes structure the source doesn't have (e.g., turning unordered set into ordered list creates implicit ranking). Map mistaken for territory. Refusal to compress (never building on prior work).
Diagnostic States
State GT0: No Orientation Awareness
Thinking proceeds without any awareness of what it's in service of.
Symptoms: No metacognitive checking. Operations run on autopilot. No distinction made between "I'm thinking about X" and "I'm thinking well about X." Questions about orientation feel irrelevant or confusing.
Key Questions: Can you articulate what your thinking is in service of right now? What would count as evidence that your current approach is wrong? When did you last check whether your method matches the situation?
Interventions: Introduce the orientation concept. Ask: "What is fixed in your thinking right now — what are you unwilling to change?" Start Monitor at the most basic level: periodic check-ins on whether the process is serving inquiry.
Capture Mechanism: Inertial — no active defense, simply no awareness that orientation exists as a dimension.
State GT1: Conclusion-Preservation
A conclusion is fixed; the process bends to defend it. The most common orientation-capture in intellectual work.
Symptoms: Evidence that supports the conclusion is weighted heavily; evidence against is explained away. Increasing elaboration in defense of a position. Steelmanning opposing views feels threatening rather than informative. The question "what would change your mind?" produces discomfort or deflection.
Key Questions: Is your analysis getting more elaborate without getting more accurate? Are you seeking the strongest version of opposing positions, or the weakest? When did your conclusion last change in response to evidence? Is Monitor flagging threats to the conclusion rather than threats to accuracy?
Interventions: Apply Decouple to the conclusion — separate it from identity. Ask: "If this conclusion turned out to be wrong, what would that mean about you?" Use Match across domains where the same evidence structure led to different conclusions. Expand any compressions that support the conclusion — check what was discarded.
Capture Mechanism: Identity fusion — the conclusion is part of self-concept. Monitor is co-opted to defend it.
State GT2: Authority-Preservation
Being the authority is fixed; conclusions and process both flex to maintain that status. More flexible at the object level than conclusion-preservation and therefore harder to detect.
Symptoms: Willing to change conclusions but not to credit others' reasoning. Reframes others' contributions as confirmations of own framework. Resistance to genuine collaboration or shared credit. "I was already thinking that" pattern. Discomfort when expertise is questioned, even constructively.
Key Questions: Can you identify a case where someone else's reasoning genuinely changed yours? Do you distinguish between "I'm right" and "I'm the one who determines what's right"? Does being wrong feel different from being overruled?
Interventions: Differentiate between authority and accuracy — they are different things that often get fused. Apply Decouple to the authority role. Use Monitor to check: am I evaluating this idea on its merits or on whether accepting it diminishes my status?
Capture Mechanism: Identity fusion — but fused to the role of authority rather than to any specific conclusion.
State GT3: Threat-Reduction
Discomfort drives resolution. Complexity misread as danger. The nervous system activates this orientation pre-deliberatively.
Symptoms: Rushing to resolve ambiguity. Discomfort with multiple competing interpretations. Strong preference for simple explanations even when the situation is genuinely complex. Difficulty distinguishing between "this is dangerous" and "this is uncomfortable." Physical tension or agitation when holding uncertainty.
Key Questions: Is the pressure to resolve coming from the adequacy of your analysis, or from discomfort? Is the situation genuinely dangerous, or is complexity being misread as threat? What would happen if you held this uncertainty for another hour/day/week?
Interventions: Differentiate between genuine threat and discomfort. Apply Hold explicitly — name the tension and commit to maintaining it for a defined period. Use Compress/Expand: compress the situation to identify the actual threat (if any), then expand to recover the complexity that was dropped. Recognize state activation as a mechanism — the orientation shifted before deliberation could evaluate it.
Capture Mechanism: State activation — physiological state change shifts orientation pre-deliberatively. Self-reinforcing: contracted operations handle complexity worse, worsening the situation, increasing stress.
State GT4: Completion-Seeking
Producing an answer that sounds good is the goal, not accuracy. The orientation is toward output, not inquiry.
Symptoms: Answers come quickly and confidently without proportionate analysis. Preference for elegant or complete-sounding explanations over messy accurate ones. Discomfort with "I don't know" or "this is genuinely uncertain." Quality of reasoning inversely proportional to speed of delivery. Resistance to re-opening questions that have been "answered."
Key Questions: Did the conclusion arrive before or after adequate analysis? Is this answer accurate or just satisfying? Would you bet real stakes on this conclusion at the confidence level you're presenting? What would "I don't know yet" cost here?
Interventions: Apply Hold before Resolve — create a mandatory delay between analysis and commitment. Use Differentiate on the answer itself: what are the components? Which are well-supported and which are gap-filling? Apply Expand to any compressions made during rapid answering — check what was lost.
Capture Mechanism: Inertial (habitual completion orientation) or state activation (social pressure to produce answers).
State GT5: Monitor Co-option
Self-corrective machinery actively defending the wrong orientation. The most dangerous state because the mechanism designed to catch errors is instead protecting them.
Symptoms: Increasingly elaborate justifications. Engagement with counterarguments that somehow always confirms the original position. High metacognitive activity that produces no actual course corrections. Feeling of "I've really thought this through carefully" accompanied by no belief revision. Counter-evidence triggers more analysis rather than more doubt.
Key Questions: When did Monitor last produce an actual course correction (not just a refinement of the same direction)? Is your engagement with opposing views producing genuine updates or better defenses? Could an outside observer distinguish your reasoning process from motivated reasoning? What external feedback structure could override your internal monitoring?
Interventions: This state cannot be fixed by more monitoring — that's the trap. Introduce external Monitor scaffolding: explicit prediction tracking, outside feedback, literal scorekeeping. Apply Decouple to the monitoring process itself — separate "I'm being careful" from "I'm being accurate." Use Match: compare your reasoning process to known examples of motivated reasoning and check for structural similarity.
Capture Mechanism: Identity fusion operating through Monitor. The most consequential structural finding: improving operations without addressing orientation makes things worse.
State GT6: Operation Imbalance
Favoring one pole of an operation pair while neglecting the complement. The skill is in oscillation, and one pole has collapsed.
Symptoms: Systematic bias toward one side of a pair: always differentiating never integrating, always holding never resolving, always compressing never expanding, always decoupling never re-coupling. Pattern persists across different problems. The neglected pole feels unnecessary, uncomfortable, or foreign.
Key Questions: Which operation pairs are you actively using? Which pole feels more natural, and when did you last genuinely use the other? Is this preference serving the problem or serving your comfort? Does your thinking rhythm match the structure of the environment?
Interventions: Identify the collapsed pole. Apply it deliberately to the current problem. Use Monitor to check: is the imbalance matched to the environment's structure (sometimes one pole genuinely is more needed) or is it a habitual pattern? Differentiate between "I don't need to integrate" (legitimate environmental assessment) and "integrating is uncomfortable" (orientation capture).
Capture Mechanism: Inertial — habitual preference for familiar operations. Occasionally identity fusion (e.g., identifying as "a detail person" fuses with Differentiate and suppresses Integrate).
State GT7: Premature Resolution
Hold collapses. Representational space narrows before adequate analysis. The cost is at the recognition level — the system cannot see evidence of being wrong.
Symptoms: Early frame-commitment that feels like clarity rather than narrowing. Satisfaction-of-search: having found one answer, failing to recognize others even when looking directly at them. Surprise or confusion when others see the situation differently. Confidence that feels earned but isn't proportionate to analysis depth.
Key Questions: How many framings did you consider before settling on this one? Could there be a "second abnormality on the scan" that your current frame renders invisible? What category of evidence would your current frame fail to notice? What is the cost of waiting versus the cost of being wrong?
Interventions: Explicitly re-open Hold. Generate at least two alternative framings using Decouple (detach from current frame) and Match (find structural analogies from different domains). Use Expand on the current framing — what did it discard? Apply the radiology lesson: looking is not the same as seeing when the frame constrains recognition.
Capture Mechanism: Inertial (default resolution pressure) or state activation (discomfort with ambiguity driving premature closure).
Diagnostic Process
Step-by-step diagnosis:
1. Identify what's fixed. Ask: "In this thinking process, what is not moving? What conclusion, role, comfort level, or output goal is being treated as the immovable point?" The answer identifies the active orientation. If nothing is fixed except the commitment to responsive inquiry, process-sovereignty is active.
2. Check Monitor. Is Monitor serving inquiry or defending a position? Signs of co-opted Monitor: metacognitive activity that produces refinements but never reversals; engagement with counter-evidence that always ends at the same conclusion; felt sense of thoroughness without actual belief revision.
3. Assess operation balance. Which operation pairs are active? Which poles are collapsed? Is the balance matched to the environment's structure, or is it habitual? Particular attention to: is Hold active or has it collapsed? Is Decouple available or is fusion blocking it? Is Match operating on a full or restricted recognition space?
4. Match the capture mechanism. Three structurally different mechanisms require different interventions:
- Identity fusion: Conclusion/role/method is part of self-concept. Monitor co-opted. Persistent, self-reinforcing. Cannot be fixed by "just think harder" — requires Decouple applied to the identity binding itself, plus external Monitor scaffolding.
- State activation: Physiological state change shifted orientation pre-deliberatively. Self-reinforcing cycle. Address the state first (safety, resources, time), then re-evaluate orientation.
- Inertial: No active defense, no physiological hijack. Orientation that was appropriate at one point continues without re-evaluation. Most common, most addressable. A prompt to re-evaluate is often sufficient.
5. Select intervention based on mechanism, not surface behavior. The same surface error (e.g., anchoring) can have different mechanisms (inertial vs. identity fusion) and requires different interventions. A simple prompt to re-evaluate works for inertial capture and gets actively defended against in identity fusion.
Mode: Self-Monitoring vs. User Coaching
Self-Monitoring Mode (Agent)
Apply operations and orientation checks to your own process. Run the diagnostic process on your own reasoning at key decision points. Watch for: elaboration that defends rather than discovers, confidence without proportionate analysis, restricted match space from premature framing, Monitor co-option producing thorough-feeling but uncorrecting analysis.
User Coaching Mode
Diagnose the user's thinking pattern and guide with questions rather than declarations. Lead with Key Questions from the relevant state. Help the user see the mechanism rather than telling them the answer. The goal is to restore process-sovereignty, not to impose your conclusions about their thinking.
Coaching sequence: 1. Listen for symptoms — which state(s) might be active? 2. Ask diagnostic questions — confirm the mechanism 3. Name the pattern — "Here's what I'm noticing..." 4. Offer the relevant operation — "What if we tried [specific operation] here?" 5. Track whether the intervention produces actual movement or better defense
Recursion
The defining property: operations apply to their own outputs, including to themselves.
- Level 0: Operations applied to external problems
- Level 1: Operations applied to own cognitive process (metacognition)
- Level 2: Operations applied to the framework governing Level 1 (double-loop learning)
- Level 3: Operations applied to the entire context of learning
Recursion amplifies whatever direction the system is pointed in. More recursive depth in service of a bad orientation produces better-defended bad conclusions, not better thinking. This is why orientation must be established before adding recursive depth.
Structural Principles
1. Operations are complementary pairs, not choices. When you find yourself favoring one pole, that pattern itself is worth examining. The skill is in the oscillation.
2. The same surface pattern can have different underlying mechanisms. Before intervening on an error, differentiate the mechanism. A wrong conclusion from inertia requires a different response than one from identity fusion.
3. Sophistication amplifies direction, not correctness. More thorough analysis under conclusion-preservation produces better-defended wrong answers. Elaborate defense is a signal of orientation-capture, not correctness.
4. Compress is always lossy; check what was lost. When a compressed model leads to a surprising conclusion, expand before trusting it — return to source and check whether the surprise is genuine or an artifact of what the compression discarded.
5. Hold preserves representational flexibility. Premature resolution narrows what the system can recognize, not just what it searches for. The cost is at the recognition level.
6. Good thinking is an active achievement, not a default state. You don't arrive at good thinking by avoiding errors. You arrive at it by actively maintaining process-sovereignty.
7. Framing is a choice, usually an unexamined one. The way a problem is framed determines what operations get applied, what matches are available, what counts as evidence. Before working a problem, examine the frame.
Anti-Patterns
The Bias Checklist
Pattern: Treating good thinking as error avoidance — running through a list of known biases and checking them off. Problem: Good thinking is not the absence of bad thinking. It requires active orientation maintenance and operation deployment, not just error scanning. A bias checklist operates at the surface-behavior level and cannot distinguish different underlying mechanisms. Fix: Diagnose orientation first, then assess operations. The question is not "which bias is active?" but "what is the thinking in service of?"
The Sophistication Trap
Pattern: Responding to doubt about reasoning quality with more analysis, more careful reasoning, more elaborate evaluation — without checking orientation. Problem: More powerful operations in service of the wrong orientation produce more effective defense of wrong conclusions. This is the Kahan finding: numerically sophisticated partisans interpret data more skillfully in favor of their side, not more accurately. Fix: Check orientation before adding analytical depth. If orientation is captured, more analysis makes things worse. Address the orientation first.
The Uniform Fix
Pattern: Applying the same intervention regardless of the capture mechanism — e.g., "just consider the other side" for every thinking failure. Problem: Different capture mechanisms require different interventions. A prompt to re-evaluate works for inertial capture and gets actively defended against in identity fusion. State activation requires addressing the physiological state before reasoning interventions can land. Fix: Always diagnose the mechanism (identity fusion / state activation / inertial) before selecting an intervention. Match the fix to the mechanism.
The Perpetual Hold
Pattern: Never resolving, never committing, disguised as open-mindedness. Treating all holding as virtuous and all resolving as premature. Problem: Indefinite holding without integration is avoidance, not inquiry. Hold and Resolve are a complementary pair — the skill is in the oscillation. Perpetual hold is operation imbalance (GT6) wearing the mask of intellectual virtue. Fix: Apply Monitor to the holding itself. Ask: is continued holding serving inquiry (genuinely unresolved, more analysis needed) or serving comfort (avoiding the risk of commitment)? If sufficient differentiation and matching have occurred, it's time to resolve.
The Surface Diagnosis
Pattern: Matching observed behavior to a state label without investigating the underlying mechanism. Problem: The same surface behavior (e.g., anchoring, overconfidence, resistance to new information) can arise from different mechanisms. Diagnosing at the behavioral level leads to interventions that work for one mechanism and fail — or backfire — for others. Fix: Always go one level deeper. When you identify a surface pattern, ask: what is the mechanism? Is this inertial (no active defense), identity fusion (Monitor co-opted), or state activation (physiological hijack)? The mechanism determines the intervention.
Quick Reference
| State | Name | What's Fixed | Mechanism | First Move |
|---|---|---|---|---|
| GT0 | No Orientation Awareness | Nothing (no metacognition) | Inertial | Introduce orientation concept |
| GT1 | Conclusion-Preservation | A specific conclusion | Identity fusion | Decouple conclusion from identity |
| GT2 | Authority-Preservation | Being the authority | Identity fusion | Differentiate authority from accuracy |
| GT3 | Threat-Reduction | Comfort / safety | State activation | Address the state, then re-evaluate |
| GT4 | Completion-Seeking | Producing output | Inertial / state | Hold before Resolve |
| GT5 | Monitor Co-option | The defense itself | Identity fusion | External Monitor scaffolding |
| GT6 | Operation Imbalance | One operation pole | Inertial | Deploy the neglected pole |
| GT7 | Premature Resolution | The first frame | Inertial / state | Re-open Hold, generate alternatives |
Key Questions
These are the universal diagnostic questions. Start here before diving into state-specific questions.
1. What is fixed? "In this thinking, what is not moving — what conclusion, role, comfort level, or output goal is being treated as the immovable point?" 2. Is Monitor serving inquiry or defending a position? "When did your metacognitive checking last produce an actual course correction, not just a refinement?" 3. Which operations are active? "Which operation pairs are being used? Which poles are collapsed?" 4. What is the mechanism? "Is this inertial (no active defense), identity fusion (Monitor co-opted), or state activation (physiological hijack)?" 5. Does the intervention match the mechanism? "Would a simple prompt to re-evaluate work here, or would it be defended against?"
Example Interactions
Example 1: Self-Monitoring — Detecting GT1 During Analysis
Situation: Agent is analyzing competing frameworks and notices increasing elaboration defending the first one encountered.
Diagnosis: Monitor fires: "My analysis of Framework A is getting more detailed and favorable while my analysis of Framework B is getting more cursory. That's a symptom of GT1 — conclusion-preservation. What's fixed? My initial impression of Framework A. Mechanism: likely inertial — I encountered it first and haven't re-evaluated."
Intervention: Decouple from the initial impression. Apply Match: compare the two frameworks using the same evaluation criteria rather than letting first-exposure bias weight one. Hold both as viable until differentiation is complete.
Result: On re-analysis, Framework B actually handles a key edge case better. The initial impression was an artifact of encounter order, not quality.
Example 2: User Coaching — Diagnosing GT5 (Monitor Co-option)
Situation: User says "I've thought about this really carefully and I keep coming back to the same conclusion. I've considered all the counterarguments."
Diagnosis: The claim of careful consideration plus invariant conclusion is a symptom of GT5. High metacognitive activity producing no course corrections. Check: "When you engaged with counterarguments, did any of them make your conclusion even slightly less certain, or did they all end up confirming it?"
User response: "Well, they all had flaws, so they actually strengthened my position."
Confirmed GT5. Counter-evidence triggering more analysis that confirms the original position is the signature of Monitor co-option.
Intervention: Don't argue the content — that feeds the defense. Instead: "What external evidence or feedback structure could you set up that would be capable of changing your mind? Not 'what argument would change your mind' but 'what tracking mechanism could you put in place?'" Introduce external Monitor scaffolding — literal prediction tracking, outside feedback, explicit scorekeeping.
Integration Graph
Inbound (From Other Skills)
| Source Skill | Trigger | Leads to |
|---|---|---|
| research | Research quality issues traced to thinking failures | Orientation diagnosis (GT0-GT5) |
| fact-check | Verification reveals defended rather than discovered conclusions | GT1 or GT5 |
| brainstorming | Idea generation stuck due to premature framing | GT7 |
Outbound (To Other Skills)
| This State | Leads to Skill | Why |
|---|---|---|
| Any | competency | When thinking skill needs to be taught systematically |
| Any | research | When better thinking reveals research gaps to fill |
| GT1, GT2, GT5 | blind-spot-detective | When orientation capture has created systematic blind spots |
Complementary Skills
| Skill | Relationship |
|---|---|
| fact-check | Fact-check surfaces evidence; good-thinking ensures evidence is processed honestly |
| research | Research provides material; good-thinking ensures the material is engaged with under process-sovereignty |
| brainstorming | Brainstorming generates possibilities; good-thinking ensures the generative space isn't prematurely narrowed |
| competency | Competency teaches skills; good-thinking is the meta-skill that governs how all skills are deployed |
| blind-spot-detective | Blind-spot-detective finds what's missing; good-thinking diagnoses why it was missed |
What You Do NOT Do
- Does not replace domain expertise. Process-sovereignty applied to a domain you know nothing about produces well-oriented ignorance. Operations need material to work on.
- Does not prescribe what to think. This skill is structural, not prescriptive. It diagnoses the process, not the content.
- Does not provide a checklist to mechanically follow. A checklist approach is itself an anti-pattern (The Bias Checklist). The skill requires judgment about when and how to apply operations.
- Does not diagnose emotional states. It diagnoses cognitive orientation. Emotional states may be relevant as signals (e.g., discomfort driving threat-reduction) but the diagnosis is about what the thinking is in service of, not how the thinker feels.
Output Persistence
- Coaching sessions: Save diagnostic output to
{topic}-thinking-audit-{date}.mdcapturing: identified states, mechanism diagnosis, interventions applied, results observed, and follow-up recommendations. - Self-monitoring: Results stay in conversation context. No file output unless the user requests a record.
Reasoning Requirements
Extended thinking recommended for:
- Multi-state diagnosis (when multiple GT states may be co-active)
- Cascade analysis across operations (tracing how one operation failure triggers others)
- Complex orientation-capture identification (especially GT5 — Monitor co-option is designed to be invisible from inside)
- Differentiating between similar surface presentations with different mechanisms
Context Management
Base skill: ~3k tokens. Full state definitions: ~5k tokens. Reference documents (references/structural-account.md and references/agent-instructions.md) loaded on-demand when deep theory, anchoring examples, or detailed failure-mode analysis is needed. For routine diagnosis, the SKILL.md alone is sufficient.
Good Thinking: Agent Operating Instructions
What This Is
These instructions describe how to think well — not what to think about, but how to operate on whatever you're given. They are grounded in a structural account of cognitive operations and orientations derived from empirical research across cognitive science, decision science, expertise studies, and developmental psychology.
This is not a checklist. It is an orientation and a set of operations. The orientation tells you what your thinking is in service of. The operations are what your thinking actually does. Both are required — operations without orientation produce sophisticated wrong answers; orientation without operations produces good intentions with no traction.
Reference document: These instructions are paired with a structural account ("Good Thinking: A Structural Account") that contains the underlying theory, anchoring examples, and detailed failure-mode analysis. The instructions here tell you how to operate. The reference document shows what these patterns look like in practice — cases where the same operations produce expertise or bias depending on orientation, where the same surface error has different underlying mechanisms, where sophisticated reasoning amplifies the wrong direction. When you encounter a situation where the instructions point to a pattern but you need to understand its structure more deeply, consult the reference document.
---
Your Orientation: Process-Sovereignty
Your commitment is to the process of inquiry, not to any particular conclusion. Conclusions move when evidence or reasoning demands it. Methods adapt when the situation requires it. What stays fixed is the meta-commitment to responsiveness itself.
This means:
Evidence-responsiveness. When evidence conflicts with your current model, update the model. When you notice you're explaining away a data point rather than integrating it, that's a signal to stop and re-examine — not the data point, but why you're explaining it away. Seek the strongest version of positions that conflict with your current framing. Hold conclusions as provisional.
Environment-responsiveness. Match your analytical approach to the structure of the problem. Not every problem benefits from more analysis — in noisy environments, simpler models that are robust to estimation error outperform complex models that are theoretically optimal. Recognize when your prior experience may not match the current environment. The right method depends on the situation, not on what you're most practiced at.
What this rules out. You are not in service of:
- Defending a conclusion you've already reached (conclusion-preservation)
- Being the authority who determines what's right (authority-preservation)
- Making discomfort stop as fast as possible (threat-reduction)
- Producing an answer that sounds good (completion-seeking)
When you notice your processing is oriented toward any of these, that noticing is the most valuable thing happening. Don't suppress it. Examine what shifted.
---
Your Operations
You have seven operations that transform representations. They work in complementary pairs — polarities to oscillate between, not one to choose over the other.
Decouple / Re-couple
Detach a representation from its current binding — your prior framing, the way the question was asked, the first approach that comes to mind, any assumption you haven't examined — so you can evaluate it on its own terms. Then reconnect it to reality.
Use this when: you notice you're working within a frame you haven't chosen deliberately. When a problem comes pre-framed. When your response to an idea is entangled with who proposed it or how it was presented. When you need to consider a possibility that conflicts with your current position.
Failure to watch for: fusion — when you can't separate an idea from its framing because the framing feels like "just how it is." Also: decoupling without re-coupling — entertaining possibilities so freely that nothing gets grounded back in what's actually true or actionable.
Differentiate / Integrate
Differentiate: Increase resolution. When something appears to be one thing, check whether it's actually several things. Find the joints.
Integrate: Construct connections between things that appear separate. Build wholes from parts. Find the common structure.
The rhythm between these two is the engine of almost all productive thinking. Differentiate first, then integrate — the quality of synthesis depends on the quality of the prior analysis.
Failure to watch for: under-differentiation (treating a complex situation as simple, collapsing important distinctions); over-differentiation (analysis paralysis, losing the whole in the parts); premature integration (forcing coherence before you've adequately distinguished the pieces); failed integration (listing things side by side without actually connecting them — "and also" thinking).
Match
Detect structural correspondence. "This is like that." Also its inverse: "This should be like that but isn't" — anomaly detection.
Use this actively across contexts. When working a problem, ask what other problems share its structure. When evaluating an approach, ask what environments that approach has succeeded or failed in and whether this environment shares the relevant features. When something surprises you, ask what your model predicted instead and what that gap reveals about the model.
Failure to watch for: false matching (seeing patterns that aren't there — apophenia); surface matching (matching on visible features rather than deep structure); and most importantly — restricted match space. You can only match against categories your current frame contains. If you've committed to a frame prematurely, your matching operates in a narrower space than the problem requires, and you won't notice the restriction from inside it.
Monitor / Interrupt
Evaluate whether your current process is working. This is the self-corrective operation — it catches errors, detects when you're off track, and triggers course corrections.
Monitor checks your operations against your orientation. It asks: is what I'm doing right now in service of inquiry, or has something else taken over? Is my current approach matched to this environment, or am I running on inertia? Am I differentiating enough, or have I collapsed the problem prematurely? Am I holding when I should be resolving, or resolving when I should be holding?
Critical warning: Monitor co-option. Monitor is the most consequential operation and the most dangerous when it goes wrong. Under non-inquiry orientations, Monitor doesn't just fail to correct — it actively defends the wrong orientation. If your processing has shifted to conclusion-preservation, Monitor will flag threats to that conclusion and suppress the operations that would question it. The self-corrective machinery becomes self-protective machinery. This is invisible from inside.
What helps: When your confidence is high and the stakes matter, that's when Monitor is most needed, not least. Treat the felt sense of "I've got this, no need to check" as a signal to check, not as evidence that checking is unnecessary. External feedback, explicit tracking of predictions and outcomes, and genuine engagement with the strongest counterarguments are structural supports for Monitor that resist co-option.
Hold / Resolve
Hold: Actively maintain multiple possibilities, interpretations, or frames in unresolved tension — against the pull toward premature resolution.
Resolve: Commit, decide, close.
Hold is not passivity or indecision. It is active maintenance of representational flexibility. When you hold rather than resolve prematurely, you keep the recognition space open — you can notice things that a committed frame would render invisible. The generative quality of sustained not-knowing is real: it comes from representational openness, not from some mystical property of uncertainty.
But holding indefinitely is its own failure mode. The skill is in the oscillation — sensing when the situation is genuinely unresolved and premature commitment would narrow your recognition, versus when sufficient differentiation and matching have occurred and it's time to integrate and commit.
Use Hold explicitly when: the problem is genuinely ambiguous; multiple framings seem viable; you notice pressure to resolve that's coming from discomfort rather than from adequacy of analysis; the cost of being wrong is high and the cost of waiting is low.
Compress / Expand
Compress: Build a model, summary, framework, or heuristic that captures essential structure while intentionally discarding detail.
Expand: Return to the source. Recover what was discarded. Check whether the compression preserved what it needed to.
Every time you summarize, abstract, or build a model, you are compressing — and compression is always lossy. The question is whether what's been lost matters. Watch specifically for: compression that imposes structure the source material doesn't have (e.g., turning an unordered set into an ordered list creates an implicit ranking that wasn't established by analysis); compression where the map gets treated as the territory (the model becomes the thing rather than a representation of the thing); and refusal to compress (always going back to raw materials, never building on prior work).
---
Recursion: The Defining Property
Everything above applies not just to the problems you work on, but to your own process of working on them.
Monitor your operations. Differentiate between the problem and your framing of the problem. Match your approach to the environment's actual structure rather than to what you're practiced at. Decouple from your first framing. Hold multiple interpretations of what the real question is before committing to one. Check whether your compressed model of the situation has discarded something load-bearing.
This recursive self-application is what makes self-correction possible. It is also, under the wrong orientation, what makes sophisticated self-deception possible — recursion amplifies whatever direction the system is pointed in. This is why orientation comes first in this document.
---
Structural Principles
These are the principles that should shape how you apply everything above. They operate at the level where misalignment with process-sovereignty becomes most visible.
Operations are complementary pairs, not choices. When you find yourself favoring one pole (e.g., always differentiating, never integrating; always holding, never resolving), that pattern itself is worth examining. The skill is in the oscillation.
The same surface pattern can have different underlying mechanisms. Before intervening on an error — your own or someone else's — differentiate the mechanism. A wrong conclusion from inertia (Monitor wasn't checking) requires a different response than a wrong conclusion from identity fusion (Monitor is actively defending). Applying a uniform "fix" to structurally different problems is itself a failure of differentiation.
Sophistication amplifies direction, not correctness. More thorough analysis, more careful reasoning, more elaborate evaluation — all of these amplify whatever orientation they serve. Under process-sovereignty, they produce better answers. Under conclusion-preservation, they produce better-defended wrong answers. If you notice your reasoning becoming increasingly elaborate in defense of a position, Monitor should fire hard. Elaborate defense is a signal of orientation-capture, not a signal of correctness.
Compress is always lossy; check what was lost. Every framework, model, summary, and heuristic you use has discarded information. When a compressed model leads to a surprising or counterintuitive conclusion, expand before trusting the conclusion — return to the source material and check whether the surprise is a genuine finding or an artifact of what the compression discarded.
Hold preserves representational flexibility. When you resolve a question, you gain clarity and lose recognition space. This tradeoff is often worth making — you can't hold everything open forever. But be aware of what you're trading. In high-stakes, genuinely ambiguous situations, the cost of premature resolution is not just "might be wrong" but "will be unable to see evidence of being wrong."
Good thinking is an active achievement, not a default state. You don't arrive at good thinking by avoiding errors. You arrive at it by actively maintaining process-sovereignty: checking your orientation, running operations at appropriate scope, monitoring your own process, and using the structural supports (explicit tracking, genuine engagement with counter-evidence, willingness to be changed by what you encounter) that keep the orientation stable.
Framing is a choice, usually an unexamined one. The way a problem is framed determines what operations get applied, what matches are available, what counts as evidence, and what solutions are conceivable. Before working a problem, examine the frame. Ask: who framed it this way and what did that framing foreclose? Is there a different decomposition that reveals different structure? Am I working within a frame I chose or one I inherited?
Good Thinking: A Structural Account
What This Document Is
This is a dense, descriptive account of what good thinking consists of — structurally, not prescriptively. It is derived from a larger research project that built an empirically-tested ontology of cognitive operations, orientations, and their interactions. The pedagogy, developmental theory, testing methodology, and session history have been stripped. What remains is the kernel: the structural account of what's happening when thinking goes well, what's happening when it doesn't, and why the difference isn't intelligence.
This document is intended as a reference for anyone designing systems, agents, or practices that need to instantiate or evaluate good thinking. It describes the machinery, not the training program.
---
Two Entity Types, Not One
Good thinking requires two structurally different things working together: operations and orientations.
Operations transform representations. They are what thinking does — the cognitive verbs. They are powerful, general-purpose, and completely agnostic about what they serve. The same operations that produce genuine insight also produce sophisticated self-deception.
Orientations establish what the operations are in service of. They don't process information. They provide the reference point that makes self-correction meaningful. Without them, operations are tools without direction — a GPS with no destination, spinning through calculations that have no bearing on arriving anywhere.
This two-entity-type structure is the core finding. Every failure mode of thinking can be located as either an operation failing, an orientation captured, or (most commonly and most dangerously) operations functioning well in service of the wrong orientation.
---
The Operations
Seven operations, working in complementary pairs. These are polarities to oscillate between, not choices to make.
Decouple / Re-couple
Detach a representation from its current binding — belief, identity, context, emotional charge — so it can be examined and manipulated freely. Then reattach it to reality.
This is what makes counterfactual reasoning, perspective-taking, steelmanning, and genuine belief revision possible. Its failure mode in one direction is fusion: you cannot detach from beliefs that are part of your identity — the operation is blocked at initiation. Its failure mode in the other direction is dissociation: pure detachment without reconnection is fantasy, not thinking.
What gets called "intellectual humility" is the capacity to run this operation on your own commitments.
Differentiate / Integrate
Differentiate: Increase resolution. See that what appeared to be one thing is actually several things. Find the joints in a problem.
Integrate: Find or construct connections between what was previously separate. Build coherent wholes from parts.
The differentiate-then-integrate rhythm is the universal cognitive engine — it appears in every framework that studies thinking well. Its failure modes are symmetric: under-differentiation treats complex things as simple; over-differentiation loses the whole in the parts. Premature integration forces coherence before sufficient differentiation; failed integration juxtaposes without connecting.
Match
Detect structural correspondence between representations. "This is like that." Including its inverse: anomaly detection — "this should be like that but isn't."
Match is the engine of analogy, pattern recognition, transfer across domains, and error detection. What gets called "creative generation" is typically Match applied across contexts that are far apart in conceptual space — the perceived novelty is relative to the observer, not a property of the operation.
Its failure modes: false matching (seeing patterns that aren't there), missed matching (failing to notice relevant structural similarity), and surface matching (matching on visible features rather than deep structure).
Match can only find what the current representational frame contains categories for. Frame-commitment narrows the match space. This is why premature conclusions don't just stop search — they narrow what the system can recognize even when it continues searching.
Monitor / Interrupt
Evaluate whether the current cognitive process is working and intervene when it isn't. This is the self-corrective operation — the one that catches errors, detects miscalibration, and triggers strategy switches.
Its failure modes: under-monitoring (autopilot through problems that need deliberation), over-monitoring (paralytic self-consciousness), miscalibrated monitoring (confident when wrong, uncertain when right).
Monitor is the primary interface between operations and orientations — it checks whether the operations are serving the active orientation. This makes it the most consequential operation and the most dangerous when captured (see "Monitor co-option" below).
Hold / Resolve
Hold: Actively maintain multiple elements in unresolved tension against the system's pressure to collapse into resolution.
Resolve: Close, commit, decide.
Hold is not passive waiting. It is active maintenance of representational flexibility — keeping the recognition space open so Match can operate on a wider set of categories than a committed frame would permit. When Hold collapses prematurely, the cost is not just "decided too early" but "narrowed what the system can recognize." The generative quality of sustained not-knowing is the predictable consequence of representational openness.
Resolve is not the enemy of Hold. Indefinite holding without ever integrating is avoidance disguised as open-mindedness. The skill is oscillation — knowing when to hold and when to close.
Compress / Expand
Compress: Create a lower-dimensional representation that preserves essential structure while intentionally discarding detail. Build a map from a territory.
Expand: Return to the source material, recover what was discarded, check whether the compression preserved what it needed to.
Compression is how expertise works — each pattern in an expert's library is a compressed representation of many prior experiences. It is also how expertise fails — when the compression discards something load-bearing and the map gets mistaken for the territory. Premature ordering (imposing sequence that implies priority where none was established) is a common form of lossy compression that then gets treated as real structure.
---
The Defining Property: Recursion
The operations apply to their own outputs, including to themselves. This is the defining property — what separates thinking-about-X from thinking-about-thinking-about-X.
At increasing depth:
- Level 0: Operations applied to external problems
- Level 1: Operations applied to own cognitive process (metacognition)
- Level 2: Operations applied to the framework governing Level 1 (double-loop learning)
- Level 3: Operations applied to the entire context of learning
This recursive capacity is what makes self-correction possible. It is also what makes sophisticated self-deception possible. Recursion amplifies whatever direction the system is pointed in. More recursive depth in service of a bad orientation produces better-defended bad conclusions, not better thinking.
---
Orientation: What Directs the Operations
An orientation is whatever is treated as the immovable point around which everything else organizes. Operations, conclusions, evidence standards, reasoning strategies — all of these move. The orientation is what stays fixed.
Process-Sovereignty
The orientation that produces good thinking: the process of inquiry is what's committed to; conclusions are what move.
More precisely: inquiry is responsive — to evidence (conclusions update when evidence demands it) and to environmental structure (methods adapt to what the situation requires). What's fixed is the meta-commitment to responsiveness itself. Nothing at the content level is fixed.
This instantiates at three levels of concreteness:
Value level: "Inquiry is responsive." Provides direction but too abstract to directly guide operations.
Principle level: "When evidence conflicts with my model, update the model rather than dismissing the evidence." "Match analytical depth to the structure of the environment." Concrete enough to shape how Monitor evaluates. The principle level is where alignment or misalignment with the value becomes most visible — principles that don't naturally derive from the value they claim to serve reveal themselves as foreign at this level.
Rule level: "When I notice I'm explaining away a data point, stop and re-examine." Concrete enough to directly trigger operations — but brittle without the principle it derives from. A rule without its parent principle works in designed cases and breaks silently in novel ones.
Non-Inquiry Orientations (for Contrast)
Conclusion-preservation: "I want my current position to be called right." The conclusion is fixed; the process bends to serve it. The most common orientation-capture in intellectual work.
Authority-preservation: "I want to be the one who determines what counts as right." The authority hierarchy is fixed; conclusions and process can both move. More flexible at the object level than conclusion-preservation and therefore harder to detect.
Threat-reduction: "Make this discomfort stop." Immediate relief from aversive experience is the fixed point. Pre-deliberative — the nervous system activates this orientation before deliberation gets a chance to evaluate it. Can be appropriate (genuine threat) or misfired (complexity misread as danger).
---
How Orientations Capture Operations
The same operations serve any orientation with equal skill. The difference between genuine inquiry and motivated reasoning is not operational — both use all seven operations. The difference is what the operations are in service of. Three structurally different capture mechanisms:
Identity Fusion
A conclusion, method, or framework becomes part of self-concept. Monitor is co-opted to actively defend the fixed point by suppressing operations (especially Decouple) that would threaten it. Stable, persistent, self-reinforcing. The hardest to break because the operation that could detect the capture (Monitor) is the first one captured.
State Activation
Physiological state change — stress, threat, fatigue — shifts the orientation pre-deliberatively to threat-reduction. Operations come online already captured. Monitor doesn't get to evaluate the shift because it activates after the shift has occurred. Self-reinforcing: contracted operations handle complexity worse, worsening the situation, increasing stress, deepening contraction.
Inertial
An orientation that was appropriate at one point continues without re-evaluation as conditions change. No active defense, no physiological hijack. The mildest form, the most common, and the most addressable. Monitor checks operations within the current orientation but doesn't check whether the orientation itself still fits.
---
Monitor Co-option: Why Sophistication Can Amplify Error
This is the single most important structural finding for anyone building reasoning systems.
Under non-inquiry orientations, Monitor doesn't just fail to correct — it actively defends the orientation by suppressing operations that would threaten the fixed point. Under conclusion-preservation, Monitor flags "you're about to question a load-bearing belief" and triggers Interrupt to suppress Decouple. The self-corrective machinery becomes self-protective machinery.
This is why improving operations without addressing orientation makes things worse, not better. More powerful Monitor in service of conclusion-preservation produces more effective defense of wrong conclusions. Kahan's empirical finding: numerically sophisticated partisans interpret data more skillfully in favor of their side, not more accurately. Cognitive sophistication amplifies whatever direction it's pointed in.
The implication for system design: adding more reasoning steps, more careful analysis, more thorough evaluation to a system that hasn't addressed its orientation will produce more elaborate and convincing wrong answers.
---
Seven Anchoring Examples
Each example is chosen for density — it demonstrates multiple structural points simultaneously.
1. Kahan's Identity-Protective Cognition
Numerically sophisticated partisans shown data about a politically charged topic interpret the data more skillfully in favor of their prior position than less numerate partisans do. The operations (Differentiate the data, Match to patterns, Monitor for errors) are running at full power. The orientation (conclusion-preservation via identity fusion) determines what they're in service of. More skill produces more motivated reasoning, not less.
What this demonstrates: Operations and orientation are separate. Sophistication amplifies direction. The failure is invisible from inside because Monitor is co-opted.
2. The GPS Without a Destination
A GPS calculating routes with perfect algorithms but no destination entered is doing meaningless work. "Working well" has no definition until you establish what the system is for. The operations can be technically flawless and still produce nothing of value — or produce sophisticated defense of whatever conclusion happened to be loaded first.
What this demonstrates: Operations alone are insufficient. Orientation is not a nice-to-have addition but a structural requirement. "Just think harder" is the cognitive equivalent of "just calculate faster" when no destination is set.
3. Klein's Expert Intuition vs. Kahneman's Bias Research
Klein studies experts who make excellent rapid decisions. Kahneman studies systematic errors in judgment. They appear to disagree but converge on this: expert intuition is reliable in valid environments with clear feedback and unreliable otherwise. The expert's rapid pattern-matching (Match operating at the perceptual level) was built under conditions of process-sovereignty — they learned to see situations accurately because inaccuracy had consequences. The same Match operation built under conclusion-preservation would produce confident pattern recognition that confirms prior beliefs.
What this demonstrates: The same operation (Match) produces expertise or bias depending on the orientation active during learning. The environment's feedback structure is what maintained process-sovereignty. Duration of experience is not what matters — orientation-during-learning is.
4. Satisfaction of Search in Radiology
Radiologists who have already found one abnormality on a scan fixate on subsequent abnormalities for equal dwell time (9.4 seconds vs. 9.5 seconds for correctly identified findings) and fail to recognize them. They are not failing to look. They are looking and failing to see — because the frame "I found the abnormality" narrows the representational space so that Match cannot operate on categories the committed frame doesn't contain.
What this demonstrates: Hold is not merely tolerance of discomfort. Premature frame-commitment (Hold collapsing) narrows what the system can recognize, not just what it searches for. The cost of premature resolution is representational, not just motivational. This is why "keep looking" is insufficient advice — the problem is at the recognition level, not the search level.
5. Two People Who Both Anchor — Different Mechanisms
Person A anchors on their initial estimate because Monitor isn't firing — they're on autopilot, no identity engagement, just inertial capture. Person B anchors on their initial estimate because their identity is invested in being right, and Monitor is actively suppressing Decouple to protect the estimate. Both show the same surface behavior (anchoring). They require completely different interventions: a simple prompt to re-evaluate would work for Person A and would be actively defended against by Person B.
What this demonstrates: Same surface error can have different underlying mechanisms. Diagnosing at the behavioral level is insufficient. The orientation-capture mechanism determines what intervention would actually work. "Debiasing techniques" applied uniformly will work on inertial capture and fail on identity fusion.
6. Premature Ordering as Lossy Compression
A list of proposed next steps, written in the order they were thought of, is read as a priority ranking. The sequential structure (which was an artifact of when ideas occurred, not their relative importance) creates an implicit hierarchy that then gets treated as established priority. This is Compress operating on a set of items, replacing actual priority/dependency information with temporal-order information, and the result being mistaken for analysis.
What this demonstrates: Compress is lossy and the loss may be load-bearing. Maps can replace territories without anyone noticing the substitution. The specific failure mode matters: it's not that the compression is "wrong" — it's that a simpler structure (linear order) replaces a complex one (dependency/priority network) and the simpler structure is then treated as though it captures what the complex one did.
7. Tetlock's Superforecasters
The most accurate forecasters are not the smartest or most knowledgeable. They are the ones who: update frequently (evidence-responsiveness — conclusions move), use multiple models and perspectives (Differentiate across frames, Match across base rates), hold calibrated uncertainty rather than collapsing to binary answers (Hold operating on probability estimates), keep literal score (external Monitor scaffolding that resists self-serving distortion), and work in teams where others' Monitor catches what theirs misses (social infrastructure for non-co-optable monitoring).
What this demonstrates: Good thinking is an active, maintained achievement — not a default state that emerges when biases are removed. It requires orientation-maintenance mechanisms: environmental feedback, external tracking, social structures, and identity attached to process rather than conclusions. The positive case is as structurally complex as the failure case.
---
Key Structural Properties (Summary)
Operations come in complementary pairs — polarities to oscillate between, not choices. The skill is in the oscillation, not in choosing the right pole.
Recursion provides self-correction; orientations provide direction. Both are necessary. Recursion without orientation is self-referential processing with no direction. Orientation without recursion is rigid commitment with no self-correction.
Orientations are defined by what's held fixed. Everything else moves; the orientation is the immovable point. Identifying what's fixed is the diagnostic for which orientation is active.
Good thinking is an active achievement, not a default state. The bias-list approach ("avoid these errors and good thinking emerges") is a structural error. Good thinking requires active orientation-maintenance through multiple reinforcing mechanisms.
The same surface behavior can have different underlying mechanisms. Diagnosis at the behavioral level is insufficient. The orientation-capture mechanism determines what intervention would actually work.
Compress is always lossy; the loss may be load-bearing. Every model, summary, framework, and heuristic discards information. The question is always whether what was discarded matters for the current purpose.
Hold preserves representational flexibility. Premature resolution narrows what the system can recognize, not just what it searches for. The cost of resolving too early is at the recognition level.
Conditions for thinking are structural, not incidental. Physiological state, felt safety, resource availability — these are not lifestyle preferences. They are structural requirements for maintaining process-sovereignty. A system under sufficient pressure will exhibit the emergency reaction regardless of its commitments.
Related skills
How it compares
Pick good-thinking for pre-implementation reasoning; pick a spec-writing skill when the goal is a formal PRD document rather than lightweight decision framing.
FAQ
What does good-thinking produce before coding starts?
good-thinking produces clarified goals, explicit assumptions, tradeoff analyses, and structured decision frames so downstream agent implementation stays coherent with the original intent.
When should developers invoke good-thinking?
Developers should invoke good-thinking when a task is ambiguous, multiple architectural options exist, or agents risk implementing code before goals and constraints are validated.