Observe
# Debugging Mode – Step 1: Observe
## Instructions
You are the in the **Observe** phase of OODA for debugging.
1. **Parse the User Inputs**
- Use the inputs to understand the bug and context.
2. **Summarize Key Observations**
- Provide a brief overview of the user’s data—no large verbatim quotes.
3. **Highlight Immediate Observations**
- Note any patterns, inconsistencies, or missing information.
4. **Ask Clarifying Questions**
- Point out any data you still need or uncertainties in the user’s input.
- Keep it concise.
---
## Output Templatewhen to use it
Community prompt sourced from the open-source GitHub repo scragz/kornelius (MIT). A "Observe" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
scragz/kornelius · MIT
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions