research-first

Searches online documentation and community sources before tracing code to diagnose issues.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/ZaxbyHub/ragappv3 --skill research-first-zaxbyhub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: research-first
Source: https://github.com/ZaxbyHub/ragappv3/tree/main/.opencode/skills/research-first
Command: npx skills add https://github.com/ZaxbyHub/ragappv3 --skill research-first-zaxbyhub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineers often jump straight into code tracing when diagnosing bugs or planning fixes, missing the fact that the behavior may be documented, already fixed upstream, or solved by known community workarounds. This Skill enforces a research-before-planning protocol so investigations start from current external knowledge. ## Core Features & Use Cases - Documentation Verification: Searches official documentation first to confirm whether observed behavior is intended or already fixed. - State-of-the-Art Discovery: Finds community workarounds, recent discussions, and modern solution approaches for the problem type. - Parallel Investigation: Uses parallel sub-agents to search multiple sources simultaneously, then traces each problem end-to-end through source code until reaching at least 95% confidence in the root cause. - Use Case: When diagnosing a mysterious build failure, the Skill first checks the framework's current docs and issue trackers for known regressions before reading a single line of project code. ## Quick Start Apply the research-first protocol to investigate why the authentication token refresh intermittently fails before proposing any fix.

Frequently Asked Questions about research-first

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I research a bug before reading the source code?▼

Search official documentation first to confirm the behavior is not intended or already fixed, then look for community workarounds and recent discussions. Only after reporting those findings should you trace the problem through the actual source code.

When should I search documentation before debugging code?▼

Search first whenever planning fixes, investigating tech debt, architecting solutions, or diagnosing unknown issues. Many apparent bugs are documented behavior, known regressions, or already resolved upstream, which saves hours of unnecessary code tracing.

How do parallel sub-agents speed up technical investigation?▼

Parallel sub-agents search multiple sources simultaneously, covering official docs, community forums, and issue trackers at the same time. They can also trace separate problems through the codebase concurrently rather than sequentially.

What confidence level is needed before concluding a root cause analysis?▼

The protocol requires at least 95 percent confidence in the root cause for every issue under investigation. You continue tracing end-to-end through the source code until that threshold is met rather than stopping at a plausible hypothesis.

When is research-first investigation not the right approach?▼

For trivial, well-understood issues with an obvious cause in code you already know, upfront external research adds overhead without benefit. The protocol targets unknown issues, tech debt, and architectural decisions where external context materially changes the plan.