claude-skills/docs/commands/cs-research-ops.md
Claude 7db491054b
docs: full repo doc resync (v2.9.0) — wire research-ops + compliance-os into docs site
Ran the /update-docs post-creation pipeline across the whole repo.

Docs site (MkDocs):
- generate-docs.py now covers 16 domains (added research-ops at order 15
  and compliance-os at order 16 + its embedded-agent mapping). Regenerated
  500 pages (328 skills + 89 agents + 83 commands); build passes.
- mkdocs.yml: site_description refreshed to 338/16/51+/87+ + v2.9.0; added
  the Research Operations and Compliance OS skills nav sections, the
  cs-research-ops-orchestrator + 8 compliance-os agents, and the 6
  research-ops command entries.
- docs/index.md: title, description, hero, the five "What's Inside" cards
  (338 skills, 51+ agents, 533 tools, 62 plugins, 87+ commands), corrected
  six domain-card counts, and added a Research Operations domain card.
- docs/getting-started.md: description, Vibe count, FAQ, bundles table
  (six corrected counts) + a research-ops bundle row.

Cross-platform sync (all four scripts gained a compliance-os entry):
- Codex: compliance-os 9 skills symlinked + index; unrelated run/status/
  review symlink churn reverted to keep the diff focused.
- Gemini: 9 compliance-os SKILL.md mirrors + index.
- Vibe (repo target): 9 compliance-os symlinks + index.
- Hermes/Vibe domain lists updated for future syncs.

compliance-os was a tracked 9-skill domain previously absent from the docs
site and the codex/gemini/vibe indices; it is now fully wired in.

The MkDocs `site/` build output is gitignored and excluded.

https://claude.ai/code/session_01PUNmQVE4WYvcrzpq2anC3D
2026-05-27 06:32:03 +00:00

2.3 KiB

title description
/cs-research-ops — Slash Command for AI Coding Agents Top-level Research Operations router. Classifies an enterprise research inquiry (clinical study design / R&D finance / market research / product. Slash command for Claude Code, Codex CLI, Gemini CLI.

/cs-research-ops

:material-console: Slash Command :material-github: Source

Route this inquiry through the research-ops-skills orchestrator:

$ARGUMENTS

Routing (deterministic, two-signal threshold)

Signal class Keywords Sub-skill
CLINICAL clinical trial, study design, protocol, endpoint, sample size, power, phase, biostatistics, feasibility clinical-research
RD_FINANCE R&D budget, program budget, burn, runway, F&A, indirect rate, capitalize vs expense, portfolio ROI research-finance
MARKET TAM, SAM, SOM, market sizing, survey, sampling, margin of error, segmentation, competitive intelligence market-research
PRODUCT user interview, JTBD, usability, concept test, discovery research, research repository, insight, saturation product-research
  1. Explore the workspace first — a resolving filename routes silently.
  2. Single signal or tie → one clarifying question with a recommended answer.
  3. Genuine multi-lane → highest-confidence first, run in fork, ask before chaining. Never silently chain.

Output (≤200-word digest)

  • What was analyzed
  • Top 3 findings, each anchored to a canon citation
  • Top 3 next actions with a named human owner where applicable
  • Artifact path
  • One grill challenge for the user

Hard rules

  • Clinical output is an estimate + named clinical owner — never fact.
  • Finance output surfaces assumptions; capex-vs-opex routes to a named finance owner.
  • Market size shows method (both ways) + assumptions — never a single number.
  • Product insight surfaces confidence + source count; singletons are anecdotes.

Distinct from

  • research/ (academic) — finds literature/grants/patents. This plans/funds/scopes/synthesizes.
  • ra-qm-team — regulatory submission. finance/ — corporate close. marketing-skill — campaign analytics.