zy839971925-zyy/Agent--deep-research-Workflow-Skills / integrations/deepseek-harness/skills/reasoning-workflow
reasoning-workflow
VerifiedDefault silent workflow for everyday questions, research, writing, design and engineering. Match effort to the request, resolve costly ambiguity, find specialist resources and verify the requested outcome. Explicitly selectable with “调用我的 workflow skills”.
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](relationships-and-systems.md), [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 |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |