OODAObserve → Orient → Decide → Act. Best for time-pressured operational decisions.
Category: Thinking & Reasoning
Before / After
Production deploy is failing. What do I do?
OODA Production deploy is failing. Build is red, customers are complaining, last good deploy was 2 hours ago.
What changes in Claude's response
Claude responds in 4 explicit sections: what's actually happening (Observe), what it means in context (Orient), the decision tree of options with tradeoffs (Decide), and the exact next command to run (Act). The framework forces operational thinking instead of explanatory thinking. You get a runbook, not a lecture.
When NOT to use OODA
Don't OODA design decisions or anything you have time to think about. The framework is built for situations where the cost of waiting exceeds the cost of being slightly wrong.
Codes that stack with OODA
OODA is one of 120 tested prompt prefixes. The full cheat sheet has before/after examples, warnings, combos, and 10 workflow playbooks.
See the full cheat sheet — from $5More Thinking & Reasoning codes
L99Pushes Claude to maximum reasoning depth. Less hedging, more opinion, longer answers.
/deepthinkForces Claude to reason through every layer before answering. Shows the work.
CHAINLOGICShows each reasoning step explicitly so you can verify the logic, not just the conclusion.
/blindspotsAsks Claude to find what you're missing or assuming, not what you're asking.
OVERTHINKDeliberately over-analyzes to surface details you'd normally skip past.