research-gatherer

Collect and cross-verify raw research findings from internal and external sources.

Updated May 11, 2026
One-click install
npx skills add https://github.com/rafalwizen/plugin-architecture-test --skill research-gatherer-rafalwizen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-gatherer
Source: https://github.com/rafalwizen/plugin-architecture-test/tree/main/week7/3-research-gatherer-demo/research-gatherer-standalone/skills/research-gatherer
Command: npx skills add https://github.com/rafalwizen/plugin-architecture-test --skill research-gatherer-rafalwizen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manually collecting and verifying research from scattered internal codebases, documentation, stakeholder transcripts, and external web sources is slow, inconsistent, and often misses cross-source contradictions or unsubstantiated claims. This Skill automates the end-to-end research gathering workflow to deliver raw, cited findings with confidence scoring and structured verification.

Core Features & Use Cases

  • Automatic research type classification: Detects if a question requires internal, external, or mixed research to trigger the correct source gathering strategy.
  • Parallel subagent delegation: Launches specialized gatherer agents for different source categories (codebase, docs, web, transcripts) to collect evidence in parallel.
  • Cross-source verification: Identifies contradictions between sources, tags declarative conclusions from stakeholder inputs, and produces confidence-scoped findings.
  • Structured output generation: Creates raw findings, rejected information logs, cross-source verification reports, and actor-tailored views for different stakeholders.
  • Use case: A product team investigating checkout flow issues can use this Skill to collect internal code, ticket, and user transcript data alongside external competitor and industry standard information, then verify consistency across all sources.

Quick Start

Use the research-gatherer skill to collect and cross-verify raw research findings for your question about internal system issues, competitor practices, or industry standards.

Frequently Asked Questions about research-gatherer

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

FAQPage Schema
How do I gather and verify research findings from multiple sources without missing contradictions?

Multi-source research gathering uses parallel subagent delegation to collect evidence from codebases, documentation, transcripts, and web sources, then cross-verifies findings to detect contradictions and score confidence automatically.

What is cross-source contradiction detection and how does it apply to mixed research?

Cross-source contradiction detection identifies conflicting evidence between internal and external sources. Mixed research classification triggers parallel gathering from codebases and web sources, tagging declarative conclusions and highlighting inconsistencies across all collected data.

How do I collect raw cited evidence from stakeholder transcripts and codebases in parallel?

Parallel subagent delegation launches specialized gatherer agents for different source categories like stakeholder transcripts and codebases, collecting raw cited evidence simultaneously while applying confidence scoring and structured verification reports.

Can I use automated research gathering to collect evidence without synthesizing a final report?

Automated research gathering collects and cross-verifies raw findings without synthesizing them into a final report. It outputs structured raw findings, rejected information logs, verification reports, and actor-tailored views for different stakeholders instead.

Does multi-source research gathering work for both internal system investigations and external competitor analysis?

Multi-source research gathering automatically classifies research type as internal, external, or mixed. This detects the correct strategy to collect evidence from internal codebases and documentation or external web sources and industry standards based on your question.

What are the limitations of using automated research gathering for evidence collection?

Automated research gathering limits output to raw findings and verification reports without synthesizing a final report. It requires defined source categories like codebases or transcripts and does not replace manual analysis for final conclusion formulation.