zy839971925-zyy/Agent--deep-research-Workflow-Skills / modular/skills/deep-research
deep-research
VerifiedUse when a scenario calls for real-world evidence, pre-build engineering/architecture research, or a linked hybrid; infer the route without requiring the user to label it. Keep the host-selected default model; infer proportionate workflow depth, honoring explicit depth requests such as Ultra.
| File | Kind | Size |
|---|---|---|
| LICENSE.txt | markdown | 1.0 KB |
| SKILL.md | skill md | 3.7 KB |
| references/comparative-synthesis.md | markdown | 3.2 KB |
| references/evidence-and-provenance.md | markdown | 7.3 KB |
| references/information-target-navigation.md | markdown | 7.4 KB |
| references/inquiry-and-research.md | markdown | 9.1 KB |
| references/multimodal-and-data.md | markdown | 3.4 KB |
| references/research-modes-and-methods.md | markdown | 17.3 KB |
| references/research-to-report.md | markdown | 3.0 KB |
| references/retrieval-and-observation.md | markdown | 14.2 KB |
| references/time-scenarios-and-forecasting.md | markdown | 3.6 KB |
| references/ultra-research.md | markdown | 9.7 KB |
references/time-scenarios-and-forecasting.md
View on GitHub# Time, scenarios and forecasting
**Trigger:** Changing facts, historical point-in-time reasoning, superseding versions, negative claims, forecasts, or scenarios matter.
**Reads:** events, publication/effective dates, versions, current observations, causal assumptions, horizon.
**Updates:** temporal lineage, point-in-time evidence set, bounded negative claims, scenarios/signposts.
**May invalidate:** anachronistic explanations, outdated current-state claims, unconditional forecasts.
**Exit:** time/version scope is resolved and forecasts/negative claims are bounded to warranted evidence.
**Related:** relationships and systems (route to the relevant sibling Skill if needed), [inquiry and research](inquiry-and-research.md), [evidence and provenance](evidence-and-provenance.md).
**Return:** [root workflow](../SKILL.md) → Inquiry / Synthesis.
Use for changing facts, historical reconstruction, negative claims, policy/software lineage, or uncertain futures.
## Time is part of the proposition
Separate event date, publication date, effective period, version, implementation date, access date, and retrospective correction when material. Track lineage such as:
`draft → announced → published → effective → implemented → amended/corrected → superseded/withdrawn`
A recent page can describe an old event or overwrite older text. The latest publication is not automatically the currently governing state.
## Point-in-time reasoning
When asking what an actor could have known or rationally believed at time T, reconstruct the evidence available at T. Do not contaminate contemporaneous reasoning with later outcomes, corrections, or hindsight. Later information can be used as retrospective analysis only when labeled as such.
## Negative and completeness claims
“None,” “never,” “first,” “only,” “all,” and “no evidence” require a defined universe. Record the relevant population, interval, jurisdictions, databases/source ecosystems, versions, languages, eligibility, and observability.
Prefer “I found no such record within the checked sources and period” over universal nonexistence when coverage is incomplete. Distinguish evidence of absence, absence of detected evidence, non-reporting, and inability to inspect.
## Forecasts are conditional
Define target and horizon. Separate current observations, causal assumptions, scenario conditions, and forecast judgment. Do not turn plausible narratives into fake probabilities.
For uncertain futures, use scenarios when useful. A good scenario has:
- conditions that would make it operative;
- mechanism/relationship path;
- early observable signposts;
- disconfirming signs;
- implications for the user's decision.
Do not force Bull/Base/Bear or three-scenario symmetry. The point is to expose decision-sensitive uncertainty and update as evidence arrives.
## Expectations matter
For markets, announcements, adoption, behavior, or strategic response, distinguish an event from its surprise relative to prior expectations. Do not infer expectations or positioning without evidence.
## Forecast update contract
A material forecast should expose what future observation would cause revision and in which direction. Keep this lightweight:
`forecast/scenario → signpost → expected interpretation → update direction`
For example, failure of a prerequisite by a relevant date may weaken one scenario; a regulatory implementation or observed adoption threshold may strengthen another. Update rules should follow the causal model and evidence, not arbitrary calendar checkpoints. Do not force numeric probabilities when the evidence cannot support calibration.
[← Return to root workflow](../SKILL.md)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |