Skip to content

zy839971925-zyy/Agent--deep-research-Workflow-Skills / modular/skills/execution-control

execution-control

Verified

Use when work creates durable artifacts or external side effects, delegates execution, needs authorization, or must preserve state/checkpoint/recovery semantics.

references/domain-patterns.md

View on GitHub
# Domain patterns

**Trigger:** A domain has characteristic evidence, failure, or verification patterns that materially change the generic workflow.

**Reads:** task domain, current lane, working model, effort vector.

**Updates:** domain-specific evidence/verification routes and failure checks.

**May invalidate:** generic plans that ignore domain-specific source, safety, or validation constraints.

**Exit:** domain-specific adaptations have been integrated without replacing the governing workflow.

**Related:** inquiry and research (route to the relevant sibling Skill if needed), synthesis, execution and verification (route to the relevant sibling Skill if needed).

**Return:** [root workflow](../SKILL.md) → whichever lane is active.

Use only when domain-specific methods materially change the reasoning. These are adaptations of the universal workflow, not separate mandatory procedures.

## Science and medicine

Distinguish hypothesis, mechanism, association, prediction, intervention effect, and individual outcome. Examine study design, measurement, selection, population, uncertainty, bias, corrections, and study identity. Peer review is not proof. Formal reviews need explicit eligibility, search, screening, extraction, and risk-of-bias methods appropriate to the domain.

## Technology, software, and AI

Separate documented capability, inspected implementation, configured environment, observed execution, and benchmarked performance. Resolve versions before merging evidence. For bugs and performance, inspect repo/runtime evidence before generic web commentary. Benchmarks transfer only when tasks, tools, budgets, environments, and scoring are comparable.

## Markets, business, and organizations

Combine outside-in forces with inside-out operating mechanics. Separate fundamentals, incentives, expectations, reported metrics, and market observations. Align entities, accounting periods, definitions, and point-in-time information. For decisions, identify pivotal assumptions, buffers, bottlenecks, competitive response, and signposts that would change the view.

## Policy, law, regulation, and institutions

Track jurisdiction, authority, effective dates, amendments, implementation, enforcement, and superseding text. Distinguish legal text, official interpretation, implementation practice, litigation, and stakeholder claims. “Policy exists” and “policy works as intended” are different propositions.

## History and events

Separate contemporaneous evidence from retrospective accounts. Resolve identity and chronology before causal narrative. Consider what was knowable at the time, archive/version changes, provenance of repeated stories, and alternative explanations for observed sequence.

## Products and consumer decisions

Start from the user's goals, constraints, switching/migration costs, risk tolerance, maintenance, ecosystem, total cost, and use context. Current specifications and availability may require fresh verification. User reports are useful for field behavior but need model/version/context alignment and provenance awareness.

## People, communication, negotiation

Use the human-context reference. Distinguish wording, context, plausible intent, incentives, power/relationship dynamics, and uncertainty. Do not infer stable personality, hidden motive, or diagnosis from thin evidence. In negotiation, model objectives, alternatives, constraints, information asymmetry, and likely response without pretending to know the other side's mind.

## Creative and editorial work

Research factual dependencies, audience expectations, genre conventions, references, or examples only when they materially improve the piece. The objective is the artifact, not maximal citation density. Preserve the user's intended voice and avoid laundering uncertain claims into confident prose.


## Controlled operational/process change

For changes to production systems, workflows, policies, operating procedures, or controlled artifacts, use the change-governance reference. Resolve the current baseline, affected interfaces, operator/user reality, temporary versus permanent status, readiness, rollout/rollback, monitoring, and effectiveness. “The change was implemented” and “the change is effective in operation” are separate claims.

[← Return to root workflow](../SKILL.md)
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall