القائمة
Use for multi-lane implementation waves in rust-harness when coordinating sub-agents, sequencing risk, and enforcing compile/test gates before reporting completion.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use the `at` CLI to create, execute, monitor, and complete tasks on the Auto-Tundra daemon. Covers the full bead lifecycle from sling to done.
Use when troubleshooting build failures, test failures, daemon connectivity issues, or integration errors in Auto-Tundra.
Use the Auto-Tundra HTTP API directly (via curl) for operations not exposed in the CLI, such as task updates, terminal management, GitLab/Linear queries, and Kanban board manipulation.
Use when adding features, fixing bugs, or refactoring code in any Auto-Tundra crate. Covers build, test, lint, and validation workflows.
Use for GitHub/GitLab/Linear wiring in rust-harness to remove stub-token paths, enforce env-driven credential resolution, and add regression tests for real-client behavior with safe fallbacks.
Use for local Ollama-first execution with queued multi-agent CLI workflows. Configures auto-tundra for one-human-overseer and many-agent-subscriber code refinery mode.
| name | wave-execution |
| description | Use for multi-lane implementation waves in rust-harness when coordinating sub-agents, sequencing risk, and enforcing compile/test gates before reporting completion. |
| allowed_tools | ["Bash","Read","Edit","Write"] |
| references | ["/Users/studio/rust-harness/AGENTS.md","/Users/studio/rust-harness/docs/research/wave2/WAVE2_EXECUTION_BOARD.md"] |
Use this skill when the user asks to "continue the next wave", "assign agents", or "think sequentially".
Lane: short nameOwner: logical team (Core/Bridge/Intelligence/UI)Scope: exact files + behavior changeValidation: exact commandsRollback: fallback behavior preserved?cargo check for touched crates.Always report: