Use when completion depends on asynchronous jobs, CI checks, processes, files, services, or other state that changes over time.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add ShugokiFable/Ultimate-AI-Starter-Bundle --skill condition-based-waiting --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Condition Based Waiting?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/shugokifable-condition-based-waiting-612a532a)More formats (shields.io, HTML) on the badges page.
---
name: condition-based-waiting
description: Use when completion depends on asynchronous jobs, CI checks, processes, files, services, or other state that changes over time.
---
# Condition-Based Waiting
Wait for the **condition**, not an arbitrary sleep duration.
## Pattern
1. Identify the observable success, failure, and terminal states.
2. Poll the authoritative state at a reasonable interval.
3. Stop immediately on success or a terminal failure.
4. Set a bounded timeout and report the last observed state when it expires.
5. For CI or remote jobs, bind polling to the exact run/commit/job identifier so a newer unrelated run cannot satisfy the wait.
6. After terminal success, verify the expected artifact/output exists before continuing.
A fixed sleep is acceptable only when the system exposes no observable progress signal. Never treat timeout as success.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...