← ClaudeAtlas

wait-goallisted

Implement an explicit user-invoked Goal mode as a durable, event-driven DAG across CodeWiz, Cursor, Claude Code, GitHub Copilot, and Codex. Use only when the user directly invokes wait-goal; never select it automatically from task length or complexity.
wenxueru/wait-skill · ★ 1 · AI & Automation · score 74
Install: claude install-skill wenxueru/wait-skill
# Wait Goal Run the objective as a persisted dependency graph. Manage durable graph state through `../scripts/waitctl.py goal -- ...` and submit external watchers through `../scripts/waitctl.py start -- ...`. The service delegates graph validation to `wait_goal.py` and watcher semantics to `wait_for.py`. Read [the goal protocol](../docs/wait-goal.md), [the supervisor guide](../docs/waitd.md), [the watcher protocol](../docs/wait.md), and [the client adapters](../docs/clients.md) before starting. ## Invocation - `<invoke> <objective>` starts a goal. - `<invoke> resume <state-file>` resumes from a wake-up or user request. - `<invoke> status <state-file>` reports persisted state without advancing it. - `<invoke> pause|cancel <state-file>` applies the requested control operation. Here, `<invoke>` is `$wait-goal` or `/wait-goal` according to the client. ## Core behavior 1. **Plan.** Persist the objective with `init`, retain its returned `state_file`, and add the initial nodes. Each node has one bounded outcome, dependency-backed inputs, acceptance checks, expected artifacts, and a read-only or explicit write scope. Keep tightly coupled work together. With a native Todo or plan tool, display these nodes using their IDs and include final objective verification. 2. **Load and schedule.** On start or resume, read `show`, run `check`, and rebuild the task's Todo from persisted state. Execute only the frontier returned by `ready`. Reflect successful state transitions in Todo; the