research-ops

原文涵盖的主题

• Research Ops
• Skill Stack
• When to Use
• Guardrails
• Workflow
• 1. Start from what the user already gave you
• 2. Classify the ask
• 3. Take the lightest useful evidence path first

Use this when the user asks to research something current, compare options, enrich people or companies, or turn repeated lookups into a monitored workflow. This is the operator wrapper around the repo's research stack. It is not a replacement for deep-research, exa-search, or market-research; it tells you when and how to use them together. Pull these ECC-native skills into the workflow when relevant: exa-search for fast current-web discovery deep-research for multi-source synthesis with citations market-research when the end result should be a recommendation or ranked decision lead-intelligence when the task is people/company targeting instead of generic research knowledge-ops when the result should be stored in durable context afterward user says "research", "look up", "compare", "who should I talk to", or "what's the latest" the answer depends on current public information the user already supplied evidence and wants it factored into a fresh recommendation the task may be recurring enough that it should become a monitor instead of a one-off lookup do not answer current questions from stale memory when fresh search is cheap separate: sourced fact user-provided evidence inference r

这里只展示节选，请以完整原文和当前要求为准。