research-ops-skills

Topics in the source

• Research Operations — Domain Orchestrator
• When to invoke
• Routing logic (deterministic)
• Signal table
• Workflow (Matt Pocock grill discipline)
• Step 1 — Explore before asking
• Step 2 — If still ambiguous, ONE forcing question with a recommended answer
• Step 3 — Decision-tree walk for multi-lane inquiries

The Research Operations surface is how the enterprise plans, funds, scopes, and synthesizes research across four workstreams: clinical R&D, R&D finance, market research, and product research. This orchestrator forks its context, routes your inquiry to one of four sub-skills, then returns a digest. Heavy intake (protocol drafts, program ledgers, survey exports, interview transcripts) stays in the forked context. This is the enterprise counterpart to the academic research/ domain. If your question is about finding literature, grants, or patents, use research/. If it is about planning, funding, scoping, or synthesizing research as an operational discipline, you are in the right place. | Symptom | Sub-skill | |---|---| | "We're designing a Phase 2 trial — what's the endpoint and sample size?" | clinical-research | | "What's our R&D program burn, and is this cost CapEx or OpEx?" | research-finance | | "What's the TAM for this product, and how do we survey the segment?" | market-research | | "How many users do we interview, and how do we synthesize the findings?" | product-research | Same two-signal threshold pattern as commercial-skills. Single-signal → clarifying question. Mixed signal

This is an excerpt. Refer to the complete source and its current requirements.