Use when debugging, architecture inspection, research, or repository exploration risks becoming open-ended, recursive, speculative, or disconnected from a decision.
Installs into .claude/skills of the current project.
Are you the author of Bounded Investigation?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/ihabkhaled-bounded-investigation)
---
name: bounded-investigation
description: Use when debugging, architecture inspection, research, or repository exploration risks becoming open-ended, recursive, speculative, or disconnected from a decision.
---
# Bounded Investigation
## Core principle
An investigation exists to answer one decision-enabling question, not to understand everything.
## Procedure
1. State the exact question.
2. Name the evidence source and expected decision.
3. Set maximum depth, time or attempt budget, and stop condition.
4. Search first, then read the smallest relevant source.
5. Record what the evidence proved or disproved.
6. Return the decision to the parent task; park anything else.
## Required output
Question, evidence, conclusion, parent impact, and next recommendation.
## Limits
Nesting at most 3; same strategy at most 3 attempts.
## Common mistakes
Do not replace the question with a broad audit or preserve a failed hypothesis because of sunk cost.
## Stop condition
Stop when the decision is possible, the budget is reached, or required evidence is externally unavailable.
