Research Operations — Domain Orchestrator — Research

Research Operations — Domain Orchestrator is a skill that routes enterprise research inquiries across four workstreams—clinical research, R&D finance, market research, and product research—to the appropriate sub-skill. It forks context, invokes the relevant sub-skill, and returns a concise digest with findings, next actions, and a challenge to the user.

research-ops claude-code

📂 View skill on GitHub ↗ 🚀 How to use

✨ What it does

Deterministic routing to one of four sub-skills based on signal keywords.
Forcing questions with recommended answers to lock lane-defining decisions.
Onboarding questionnaires per sub-skill to pre-configure tools.
Digest output with top findings, next actions, and a grill challenge.
Opt-in autoresearch handoff for optimization loops.
Artifact generation per sub-skill (e.g., protocol synopsis, budget, market sizing).

🎯 When to use it

When planning, funding, scoping, or synthesizing enterprise research across clinical, finance, market, or product domains.
When the inquiry involves designing a clinical study, determining sample size, or evaluating endpoints.
When managing R&D program budgets, burn rate, or capitalizing vs. expensing costs.
When conducting market sizing, survey design, or segmenting a market.
When planning user interviews, usability tests, or synthesizing product research insights.

🚀 How to use

Trigger by asking a research operations question that matches one of the four domains. The skill will explore your workspace, ask a clarifying question if needed, then route to the appropriate sub-skill. Provide any relevant artifacts (protocol drafts, budgets, survey data) in the conversation. Example prompts:

"Design a Phase 2 trial for our drug — what sample size do we need?"
"What's our R&D burn rate and should we capitalize this software cost?"
"Estimate the TAM for our new product and design a survey to validate it."
"How many user interviews do we need and how should we synthesize findings?"

📄 Output: A digest (≤200 words) with top findings, next actions, artifact path, and a challenge, plus generated artifacts like protocol synopsis, budget, market sizing, or research plan.

📦 Add this skill to Claude Code

# 1. Get the skills repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills /tmp/claude-skills

# 2. Copy this skill into your project (or ~/.claude/skills for all projects)
mkdir -p .claude/skills
cp -r /tmp/claude-skills/research-ops/skills/research-ops-skills .claude/skills/research-ops-skills

Skill source: research-ops/skills/research-ops-skills/SKILL.md

⚠️ Good to know

Requires research authority or preparation for someone with authority; outputs are recommendations with named human owners, not final decisions; does not store research history across sessions.

❓ FAQ

What is the difference between this skill and the academic research/ skill?

The academic research/ skill finds literature, grants, and patents, while this skill plans, funds, scopes, and synthesizes research as an operational discipline.

Can I run all four sub-skills at once?

No, that is an anti-pattern. The skill picks one sub-skill, digests, and chains only if needed after confirmation.

How does the skill handle ambiguous requests?

It asks one forcing question with a recommended answer, based on the signal table, to determine the correct lane before invoking a sub-skill.

🤖 Overview, features, install steps and FAQ were generated from the project's SKILL.md on Sep 4, 2026. Always check the original source before running commands.