Where does the skill store its research findings?

All findings, hypotheses, and evidence are recorded in a mandatory investigation log file located at .temp/INVESTIGATION.md.

How does Research 150 verify information?

It follows a strict verification hierarchy where production code is treated as the highest truth, followed by API models, production usage, and tests, while documentation is treated as the lowest truth.

What is the 150% scope rule?

The 150% scope rule mandates investigating 100% of the core task plus an additional 50% covering boundary areas, such as callers, consumers, and configuration dependencies.

When should I use the Research 150 skill?

Use it whenever a task requires root-cause analysis, mapping unknown areas of a codebase, or any situation where a 'probable' answer is not enough and evidence-based proof is required.

Research 150: Deep Investigation Workflow

Name: Research 150: Deep Investigation Workflow
Author: MykhailoDmytriakha

byMykhailoDmytriakha

Productivity & Workflow

Conducts deep, evidence-based research using a 150% scope methodology to map core requirements and adjacent boundaries.

About

Research 150 is a rigorous investigation skill designed for Claude Code that mandates a structured, evidence-based approach to problem-solving. By expanding research scope to 150%—covering 100% of the core task and 50% of the surrounding boundaries—it ensures developers uncover root causes, map complex dependencies, and avoid assumption cascades. The skill enforces a mandatory research log, uses cross-reference validation across production code, tests, and documentation, and employs contradiction hunting to ensure every conclusion reaches bedrock truth.

Key Features

Multi-source cross-reference validation (code, tests, and documentation)
Scope150 methodology covering core requirements and boundary dependencies
Systematic exploration framework for navigating unknown codebases
Rigorous contradiction hunting to disprove false hypotheses
Mandatory structured research log for traceability and knowledge capture
0 GitHub stars

Use Cases

Root-cause analysis for complex bugs in large, unfamiliar repositories
Mapping architectural dependencies before performing major refactors
Technical due diligence and external verification using web-integrated search

About

Key Features

Multi-source cross-reference validation (code, tests, and documentation)
Scope150 methodology covering core requirements and boundary dependencies
Systematic exploration framework for navigating unknown codebases
Rigorous contradiction hunting to disprove false hypotheses
Mandatory structured research log for traceability and knowledge capture
0 GitHub stars

Use Cases

Root-cause analysis for complex bugs in large, unfamiliar repositories
Mapping architectural dependencies before performing major refactors
Technical due diligence and external verification using web-integrated search