Evidence-first current-state research workflow for ECC. Use when the user wants fresh facts, comparisons, enrichment, or a recommendation built from current public evidence and any supplied local context.
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 discoverydeep-research for multi-source synthesis with citationsmarket-research when the end result should be a recommendation or ranked decisionlead-intelligence when the task is people/company targeting instead of generic researchknowledge-ops when the result should be stored in durable context afterwardNormalize any supplied material into:
Do not restart the analysis from zero if the user already built part of the model.
Choose the right lane before searching:
exa-search for fast discoverydeep-research when synthesis or multiple sources mattermarket-research when the outcome should end in a recommendationlead-intelligence when the real ask is target ranking or warm-path discoveryFor important claims, say whether they are:
Freshness-sensitive answers should include concrete dates.
If the user is likely to ask the same research question repeatedly, say so explicitly and recommend a monitoring or workflow layer instead of repeating the same manual search forever.
QUESTION TYPE
- factual / comparison / enrichment / monitoring
EVIDENCE
- sourced facts
- user-provided context
INFERENCE
- what follows from the evidence
RECOMMENDATION
- answer or next move
- whether this should become a monitor