run-research-pipeline
Full research workflow orchestration from knowledge elicitation to consolidated findings. PROACTIVELY activate for: (1) end-to-end research projects, (2) comprehensive analysis, (3) strategic research requiring multiple phases, (4) complex research questions. Triggers: "run research pipeline", "full research workflow", "comprehensive research", "end-to-end research", "complete research process"
What this skill does
# Run Research Pipeline
Execute a complete research workflow from problem definition through consolidated findings.
## When to Use
Use this skill when you need:
- End-to-end research on a complex topic
- Structured progression through all research phases
- Multi-LLM research design and synthesis
- Comprehensive analysis with quality gates at each phase
## Pipeline Overview
```
┌─────────────────────────────────────────────────────────────┐
│ RESEARCH PIPELINE │
├─────────────────────────────────────────────────────────────┤
│ │
│ Phase 1: ELICITATION │
│ ┌─────────────────────┐ │
│ │ research-interview │ → PROBLEM-STATEMENT │
│ └─────────────────────┘ │
│ ↓ │
│ Phase 2: DESIGN │
│ ┌─────────────────────┐ │
│ │ research-brief │ → Model-optimized prompts │
│ └─────────────────────┘ │
│ ↓ │
│ Phase 3: EXECUTION (User) │
│ ┌─────────────────────┐ │
│ │ Run prompts in │ → Raw model outputs │
│ │ Claude, Gemini, GPT │ │
│ └─────────────────────┘ │
│ ↓ │
│ Phase 4: SYNTHESIS │
│ ┌─────────────────────┐ │
│ │ consolidate-research│ → CONSOLIDATED-REPORT │
│ └─────────────────────┘ │
│ │
└─────────────────────────────────────────────────────────────┘
```
## Workflow
Execute complete research pipeline for: "$ARGUMENTS"
### Phase 1: Knowledge Elicitation
Run `research-interviewer` to produce PROBLEM-STATEMENT:
**Objective:** Define the research question clearly with:
- Core question and sub-questions
- Key constraints and assumptions
- Success criteria
- Known information vs gaps
**Output:** `<problem-statement>` artifact with confidence scores
**Quality Gate:**
- [ ] Research question is specific and answerable
- [ ] Assumptions surfaced and examined
- [ ] Scope boundaries defined
- [ ] Success criteria measurable
### Phase 2: Research Design
Run `create-research-brief` Phase 1 to generate:
**Objective:** Design multi-LLM research strategy with:
- MECE question decomposition (5 categories)
- Model-optimized prompts for Claude, Gemini, GPT
- Risk assessment for the research approach
**Model Assignment Strategy:**
| Model | Strength | Best For |
|-------|----------|----------|
| Claude Opus 4.5 | Judgment, synthesis | Strategic questions, nuance |
| Gemini Pro 3 | Breadth, citations | Factual lookup, sourcing |
| GPT-5.2 Deep | Recency, depth | Technical details, edge cases |
**Output:** `<research-brief>` with prompts for each model
**Quality Gate:**
- [ ] MECE decomposition complete (no overlaps/gaps)
- [ ] Each sub-question independently researchable
- [ ] Model assignments match model strengths
- [ ] Prompts optimized for each model's style
### Phase 3: User Executes Prompts
**PAUSE POINT** - Display prompts for user to execute:
```markdown
## Ready for Multi-Model Research
Execute the following prompts in each model:
### Claude (Opus 4.5)
[Display Claude prompt]
### Gemini (Pro 3)
[Display Gemini prompt]
### GPT (5.2 Deep)
[Display GPT prompt]
---
**Instructions:**
1. Copy each prompt to its designated model
2. Collect the responses
3. Paste all responses back here to continue to Phase 4
```
**Wait for user to provide model outputs before continuing.**
### Phase 4: Consolidation
Run `create-research-brief` Phase 2 to synthesize:
**Objective:** Produce unified findings with:
- Evidence scoring (5-point scale)
- Conflict resolution (WWHTBT protocol)
- Uncertainty classification
- MECE coverage audit
**Output:** `<consolidated-report>` with:
- Executive summary
- Findings by category with evidence scores
- Conflicts resolved and rationale
- Remaining gaps and recommendations
**Quality Gate:**
- [ ] All model outputs incorporated
- [ ] Evidence scores assigned
- [ ] Conflicts explicitly resolved
- [ ] Actionable recommendations provided
## Output Format
Final pipeline output includes all artifacts:
```xml
<research-pipeline-output>
<metadata>
<topic>$ARGUMENTS</topic>
<pipeline_id>[unique identifier]</pipeline_id>
<completed_phases>[1,2,3,4]</completed_phases>
</metadata>
<phase-1-output>
<problem-statement>...</problem-statement>
</phase-1-output>
<phase-2-output>
<research-brief>...</research-brief>
</phase-2-output>
<phase-3-inputs>
<model-response model="claude">...</model-response>
<model-response model="gemini">...</model-response>
<model-response model="gpt">...</model-response>
</phase-3-inputs>
<phase-4-output>
<consolidated-report>...</consolidated-report>
</phase-4-output>
<next-steps>
[Recommended follow-up actions]
</next-steps>
</research-pipeline-output>
```
## Quality Gates (Pipeline-Level)
- [ ] All four phases completed
- [ ] Each phase passed its quality gates
- [ ] Artifacts linked and traceable
- [ ] Final recommendations actionable
- [ ] Confidence levels appropriate for decision-making
## Post-Pipeline Options
After completing the research pipeline:
| If you need to... | Use skill... |
|-------------------|--------------|
| Evaluate options from findings | `/compare-options` |
| Get expert validation | `/run-expert-panel` |
| Document the methodology | `/write-reference` |
| Create implementation guide | `/write-howto` |
| Optimize follow-up prompts | `/optimize-prompt` |
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.