research-first
The research-first skill establishes a protocol requiring comprehensive online research of official documentation, community solutions, and recent discussions before any code analysis or fix planning begins. Use this skill when investigating bugs or problems to ensure proposed solutions are not already available, officially intended, or documented as resolved in current resources.
git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm /tmp/research-first && cp -r /tmp/research-first/.claude/skills/research-first ~/.claude/skills/research-firstSKILL.md
## Research Before Planning Protocol Before planning any fix, tracing any issue, or proposing any solution: 1. Search online for current official documentation to confirm the behavior is NOT intended or already fixed 2. Search for state-of-the-art solutions, known community workarounds, and recent discussion on this problem type 3. Use parallel sub-agents to search multiple sources simultaneously 4. Report all findings before any code tracing begins Then trace each problem end-to-end through the actual source code using parallel sub-agents. Do not stop until ≥95% confident in the root cause for every issue being investigated.
>
Run a rigorous, quote-grounded codebase review or security/QA/accessibility/performance/AI-slop/enhancement audit. Use for full-repo or large-subsystem review reports; not for normal implementation. Performs Phase 0 inventory, selected exhaustive tracks with non-diluting depth, coverage closure, reviewer/critic validation, and writes .swarm/review-v8 artifacts without modifying source files.
>
>
Use when asked to trace, investigate, root-cause, plan, fix, close, or prepare a PR for a GitHub issue or bug report. Runs an evidence-first issue workflow: GitHub intake, reproduction, reasoning-guided localization, no-gap fix planning, independent critic review, user approval gate, implementation, tests, and PR-ready closure.
>
>