flow-discover

Orchestrates multi-provider AI research and synthesizes findings into a structured report.

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/GongYuanCaiJi/dsh-claude-octopus --skill flow-discover-gongyuancaiji
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flow-discover
Source: https://github.com/GongYuanCaiJi/dsh-claude-octopus/tree/main/.claude/skills/flow-discover
Command: npx skills add https://github.com/GongYuanCaiJi/dsh-claude-octopus --skill flow-discover-gongyuancaiji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Single-model research often misses perspectives and produces biased or incomplete answers. This Skill runs the Discover phase of the Double Diamond workflow by dispatching a research question to multiple external AI providers (Codex, Antigravity, Copilot, Qwen, Ollama, Perplexity, OpenRouter, and others) in parallel, then synthesizing their outputs into one structured, source-attributed report. ## Core Features & Use Cases - Dynamic provider fleet: Uses build-fleet.sh to detect locally available providers and assign diverse perspectives, enforcing model-family diversity to reduce agreement bias. - Adjustable research intensity: Supports quick (2 agents), standard (4-5 agents), and deep (6-10 agents) modes via breadth/intensity parameters. - Structured synthesis: Produces a report with executive summary, key findings, themes, conflicts, gaps, priority matrix, recommendations, and per-provider source attribution, saved as a probe-synthesis markdown file. - Use Case: Ask "Compare Redis vs Memcached for session storage" and receive a multi-provider comparison covering implementation details, ecosystem trends, and trade-offs, with each claim attributed to its source provider. ## Quick Start Ask the assistant to research a topic with the octo discover workflow, for example: run octo research on OAuth 2.0 authentication patterns for React apps.

Frequently Asked Questions about flow-discover

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

FAQPage Schema
How do I run multi-AI research with multiple providers?▼

Invoke the discover workflow with a research question, for example "octo research GraphQL vs REST trade-offs". The skill builds a provider fleet with build-fleet.sh, launches parallel background agents via orchestrate.sh probe-single, and synthesizes the results into a structured report.

Which AI providers does the discover workflow support?▼

The fleet can include Codex, Antigravity, Copilot, Qwen, OpenCode, Ollama, Perplexity, OpenRouter, Cursor Agent, and Claude, depending on what is installed locally. The build-fleet.sh script detects available providers and enforces model-family diversity when assigning perspectives.

Can I use the discover workflow without any external providers installed?▼

Yes, the host model itself acts as one seat, but standard and deep research require at least two usable provider outputs. If all external providers are unavailable, the workflow suggests running setup and stops rather than falling back to single-model research.

How do I control the depth of the multi-provider research?▼

Pass a breadth or intensity parameter: quick uses 2 agents, standard uses 4-5 agents, and deep uses 6-10 agents across all available providers. If omitted, the workflow defaults to standard intensity.

When should I not use the discover research workflow?▼

Do not use it for simple file searches, questions answerable from existing knowledge, debugging issues, or decision-support requests about options. Those cases are handled by direct file tools, the debug skill, or the decision-support skill respectively.

What happens if some providers fail or time out during research?▼

The workflow degrades gracefully: with two or more usable results it proceeds normally, with one result it warns about reduced synthesis quality, and with zero results it reports an error. Failed providers are listed as coverage gaps, never cited as evidence.