zy839971925-zyy/Agent--deep-research-Workflow-Skills / modular/skills/execution-control
execution-control
VerifiedUse when work creates durable artifacts or external side effects, delegates execution, needs authorization, or must preserve state/checkpoint/recovery semantics.
| File | Kind | Size |
|---|---|---|
| LICENSE.txt | markdown | 1.0 KB |
| SKILL.md | skill md | 2.4 KB |
| references/domain-patterns.md | markdown | 4.2 KB |
| references/engineering-delivery.md | markdown | 2.8 KB |
| references/runtime-and-delegation.md | markdown | 9.0 KB |
| references/semantic-state-contract.md | markdown | 5.7 KB |
| references/state-model-and-invariants.md | markdown | 7.1 KB |
| references/synchronization-and-recovery.md | markdown | 8.8 KB |
| references/traceability-and-integrity.md | markdown | 6.2 KB |
references/engineering-delivery.md
View on GitHub# Engineering delivery through the normal entry point
Start at the request. If the user wants investigation, inspect and report. If they want a runnable change, trace one representative input from the normal entry through its state or data dependencies to the user's observable outcome. Prefer existing project conventions. Keep unrelated edits and incidental dependencies outside the change.
### Decide what must remain true
Read local instructions, callers, lockfiles, and existing checks relevant to the change. Identify the acceptance condition, a previous behavior or data format users rely on, and the most consequential failure. Reproduce a reported defect on a disposable copy if practical. If it cannot be reproduced, distinguish the observed symptom, suspected cause and test that could distinguish it. For unfamiliar tools, discover the appropriate specialist or check versioned documentation.
### Choose checks by failure mechanism
| Change | Useful witness | Failure worth exercising |
|---|---|---|
| Import, migration or state write | Existing data opens through the same client before and after the change | A partial write, repeated import or recovery leaves consistent state |
| CLI, API or adapter | Call the public entry with the caller's actual argument shape and inspect result and exit status | Invalid or legacy input reports the correct outcome across supported entry points |
| Distributed package | Build, unpack or install in an empty directory apart from the source repository, then exercise one normal task | A runtime asset, executable bit or relative dependency exists only in the checkout |
| UI or motion | Walk the actual interaction in both directions on the relevant viewport and inspect visible state | Cancellation, interruption, reduced motion or a changed return destination |
| Performance | Compare the same inputs and environment before/after; include units and variability | A faster microbenchmark leaves the user-visible bottleneck unchanged |
Use the smallest check that would fail on the old defect and pass on the change; preserve a meaningful unchanged control. Add a regression where the existing tests miss this behavior. Build or run broader checks when shared dependencies or release artifacts make them relevant. An expected failure caused by missing tooling is a verification gap; retain the command and scope for the report.
### Close the change
Read the diff against the request. Check generated copies and released artifacts where the project ships them. Re-run through the real entry after the final edit. Report what the user can use, what was observed, and material limits such as untested devices. If the implementation depends on unresolved product direction, narrow the change to agreed work or ask before starting expensive dependent implementation.
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 |