skills.rest
ZaxbyHub
ZaxbyHubOFFICIAL
Explore all skills by this author →
GitHub

research-first

Verify external and repository facts before implementation planning.

437|45|Updated Jan 27, 2026
Search Tags:#research#implementation planning#risk assessment#repository analysis#api validation#fact verification
One-click install
npx skills add https://github.com/ZaxbyHub/opencode-swarm --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/opencode-swarm/tree/main/.agents/skills/research-first
Command: npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill research-first-zaxbyhub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementing code based on unverified external facts or incorrect assumptions about repository behavior leads to broken functionality, wasted development time, and costly rework when plans fail in production.

Core Features & Use Cases

  • External Fact Verification: Confirms current details for unfamiliar libraries, public APIs, security advisories, release notes, and product behavior using primary official sources.
  • Repository Fact Validation: Uses local tools like ripgrep, file reads, and existing test suites to verify internal codebase behavior instead of relying on outdated memory.
  • Risk Mitigation: Requires all unresolved unknowns to be explicitly marked as risks before implementation planning begins, preventing avoidable mistakes.
  • Use Case: If you are building a feature that integrates with a new third-party payment API, use this skill first to confirm the API's current endpoints, authentication requirements, and rate limits before writing any implementation code.

Quick Start

Use the research-first skill to verify the current authentication requirements for the Stripe API before drafting the payment integration plan.

Frequently Asked Questions about research-first

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

FAQPage Schema
How do I verify external API behavior before writing integration code?▼

Verify external API behavior by checking primary official sources for current endpoints, authentication requirements, and rate limits before planning implementation. This pre-implementation fact verification separates confirmed details from assumptions to prevent broken functionality and wasted development effort.

Why does implementing code based on unverified assumptions lead to rework?▼

Implementing code based on unverified assumptions leads to rework because outdated memory or incorrect guesses about repository behavior and external library facts cause broken functionality. Pre-implementation verification using primary sources and local tools separates verified facts from risks.

How to validate internal repository logic before planning a feature?▼

Validate internal repository logic by using local code search tools like ripgrep, file reads, and existing test suites to verify actual codebase behavior. This ensures your implementation plan relies on current repository facts rather than outdated memory.

When do I need to mark unresolved unknowns as project risks during implementation planning?▼

Mark unresolved unknowns as explicit project risks during implementation planning when fact verification cannot confirm details about unfamiliar libraries, public APIs, security advisories, or internal repository logic. This prevents avoidable implementation mistakes before coding begins.

What's the best way to check public API rate limits and authentication requirements before coding?▼

The best way to check public API rate limits and authentication requirements is verifying current details directly from primary official sources before drafting any implementation plan. This confirms external facts and prevents costly rework from outdated or incorrect API assumptions.

Can I use existing test suites to confirm repository-specific behavior for implementation planning?▼

Yes, you can use existing test suites to confirm repository-specific behavior for implementation planning. Running local tests alongside ripgrep and file reads validates internal codebase logic, separating verified repository facts from assumptions before development begins.

Related Skills

Explore More Software Engineering Skills→
lushly-devlushly-dev
4

research-topics

Research unfamiliar APIs and technologies using multi-source verification workflows.

Official
Intermediate
Manvendra08Manvendra08
1

blueprint

Generate ordered executable step plans with dependency graphs and review gates.

Community
Advanced
heyallencaoheyallencao
118

ks-verify

Run automated test suites and coverage checks to validate code claims.

Community
Intermediate
ajsai47ajsai47
11

make-plan

Generate phased implementation plans with documentation references and verification checklists.

Community
Intermediate