implementation-research

Researches technical implementation patterns from official docs, GitHub, and production code into actionable recommendations.

Updated Aug 29, 2026
One-click install
npx skills add https://github.com/1arley/volibear --skill implementation-research-1arley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implementation-research
Source: https://github.com/1arley/volibear/tree/main/.opencode/skills/implementation-research
Command: npx skills add https://github.com/1arley/volibear --skill implementation-research-1arley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When facing a concrete technical problem (library choice, API usage, concurrency, integration), developers often get shallow answers or outdated blog posts. This Skill structures the investigation of how a specific technical problem is solved in practice, using a prioritized source hierarchy, and synthesizes findings into an actionable recommendation instead of a list of links. ## Core Features & Use Cases - Prioritized Source Hierarchy: Consults official documentation first, then GitHub issues/PRs and maintainer discussions, then production code, then technical articles. - Confidence-Graded Evidence: Labels findings as CONFIRMED, HIGH CONFIDENCE, POSSIBLE, or SPECULATIVE based on source authority. - Structured Synthesis Output: Produces a fixed research format covering reference, pattern, relevance, adaptation, trade-offs, and recommendation. - Use Case: When deciding how to implement cache invalidation with concurrent writes in Redis, the Skill walks from official Redis docs through GitHub issues and production implementations, then delivers a trade-off-aware recommendation. ## Quick Start Ask the agent to research the best way to implement your specific technical problem, for example how to handle concurrent cache invalidation in Redis, and request a synthesized recommendation with trade-offs.

Frequently Asked Questions about implementation-research

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

FAQPage Schema
How do I research the best way to implement a technical pattern?▼

Start with the official documentation for the canonical API or pattern, then check GitHub issues and PRs for reported gotchas, then review production code in mature projects. Synthesize the findings into a recommendation with explicit trade-offs rather than a list of links.

What sources should I trust for implementation research?▼

Use a hierarchy: official documentation first, then GitHub issues, PRs, and maintainer discussions, then production code from mature projects, then technical articles. Stack Overflow is useful for gotchas but should not replace official docs for canonical usage.

How do I handle conflicting advice between docs and blog articles?▼

Weight sources by authority: official docs and maintainer discussions outrank articles. Check article dates and versions, since benchmarks and comparisons age quickly, and downgrade confidence when a source cannot be verified.

When is official documentation alone enough for a technical decision?▼

For well-known problems with a documented canonical pattern, the official docs suffice and further research is over-investigation. Escalate to GitHub issues or production code only for edge cases, undocumented behavior, or trade-off decisions.

Can I copy production code from another project directly?▼

No. Production code from other projects rarely fits your context directly. Extract the underlying pattern and adapt it to your framework, version, and scale, while noting which parts are project-specific and should not be copied.