zy839971925-zyy/Agent--deep-research-Workflow-Skills / modular/skills/reasoning-core
reasoning-core
VerifiedUse when a task needs problem framing, representation choice, decomposition, relationships, causal chains, hypotheses, or careful interpretation.
| File | Kind | Size |
|---|---|---|
| LICENSE.txt | markdown | 1.0 KB |
| SKILL.md | skill md | 2.8 KB |
| references/clarification-gate.md | markdown | 6.9 KB |
| references/human-context-and-interpretation.md | markdown | 3.9 KB |
| references/hypotheses-and-bias-control.md | markdown | 6.2 KB |
| references/model-adaptation.md | markdown | 6.7 KB |
| references/problem-framing-and-effort.md | markdown | 7.5 KB |
| references/reasoning-structure-and-decomposition.md | markdown | 5.5 KB |
| references/relationships-and-systems.md | markdown | 4.3 KB |
| references/specialist-resources.md | markdown | 2.8 KB |
| references/worked-examples.md | markdown | 5.1 KB |
| references/writing-for-the-reader.md | markdown | 1.7 KB |
references/relationships-and-systems.md
View on GitHub# Relationships and systems
**Trigger:** Mechanisms, indirect effects, causes, consequences, feedback, context, forecasts, or cross-domain relationships can change the answer.
**Reads:** focal question/object, working model, time horizon, hypotheses, observations.
**Updates:** material relationship map, mechanisms, conditions/lags, signposts, pruned branches.
**May invalidate:** narrow problem frames, causal narratives, forecasts, actions based on missing dependencies.
**Exit:** consequential paths are supported/bounded and further expansion is low-value.
**Related:** inquiry and research (route to the relevant sibling Skill if needed), [hypotheses and bias control](hypotheses-and-bias-control.md), time, scenarios and forecasting (route to the relevant sibling Skill if needed).
**Return:** [root workflow](../SKILL.md) → Relevance / relationships.
Use when indirect connections, explanation, consequences, prediction, design trade-offs, or context outside the prompt can change the result. A relationship map is a revisable inquiry model, not proof of causation.
## Build a small map before expanding
Start from the outcome, decision, or artifact and its time horizon. Distinguish relationship types instead of collapsing them into generic “connections.” Use labels such as `causes`, `correlates_with`, `depends_on`, `enables`, `constrains`, `mediates`, `moderates`, `precedes`, `is_part_of`, `is_example_of`, and `is_alternative_to` when they improve precision. Also distinguish identity, definition, chronology, membership, ownership, evidence reuse, incentives, and proposed causal links.
For a consequential edge retain only what matters:
`from → relation → to | why it matters | mechanism/meaning | conditions/lag | observed/inferred/hypothesized | evidence/gap | alternatives`
Do not create a complete graph or expose a thought transcript.
## Inside-out and outside-in
### Inside-out
Follow the focal object outward:
- immediate consequences and intermediates;
- behavioral responses and adaptation;
- second-order effects;
- feedback into the original state;
- downstream constraints on execution.
### Outside-in
Look for external forces not named in the prompt that could materially shape the result: social, technological, economic, environmental, political/legal, infrastructure, culture, competition, suppliers, partners, institutions, or adjacent systems.
Outside-in thinking is a guard against solving only the problem as initially framed. Sample unfamiliar perspectives when the initial map may be self-confirming.
## Mechanism discipline
For A → B → C, observations of A and C do not establish either edge or mediation through B. Ask what observable evidence should exist if the proposed transition is operating and what alternative could create the same pattern.
Consider where relevant:
- upstream prerequisites and common causes;
- substitutes, complements, buffers, hedging, and workarounds;
- time lags, duration, path dependence, and reversal;
- feedback and reflexivity;
- thresholds, saturation, nonlinear response, and regime change;
- expectations versus realized events;
- confounding, selection, reverse causality, and collider-like conditioning;
- incentives and strategic behavior;
- bottlenecks and capacity constraints.
A plausible mechanism without observation remains a hypothesis. Lack of a known mechanism does not by itself refute a reproducible association.
## Forecast implications and signposts
If a relationship supports a future scenario, identify conditional implications: what should become observable first if the path is occurring? Use signposts to update the scenario rather than pretending to know an exact probability.
## Bound expansion
Follow a branch only when resolving it can change the user's interpretation, decision, forecast, design, or execution. Before a costly hop, state its possible consequence and the next discriminating observation.
Close or pause when applicability fails, the effect is immaterial, the route duplicates existing provenance, or no feasible observation can distinguish the alternatives. Keep high-consequence unresolved branches explicit. No fixed number of hops guarantees depth.
“Everything is connected” is not a research result. Connections earn attention by materiality and testability.
[← Return to root workflow](../SKILL.md)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |