AgentWeave

Orient yourself at the start of an AgentWeave session — read your assigned role from roles.json, check your inbox for unread messages, and list your active tasks. Run this automatically at the beginning of any session in an AgentWeave project.

Manage scheduled AI jobs in AgentWeave — create recurring tasks that trigger agents on a cron schedule. Usage — /aw-jobs [list|create|pause|resume|delete|run]

Delegate a task to another agent in the AgentWeave session. Usage — /aw-delegate <agent> "<task description>"

Mark a task as completed and notify the principal agent. Usage — /aw-done <task-id> ["optional completion note"]

Generate a relay prompt to hand off pending work to another agent manually. Usage — /aw-relay <agent-name>

Request a code review from another agent in the AgentWeave session. Usage — /aw-review "<what to review>" ["focus area or specific concern"]

Accept a revision request for a task that came back as revision_needed — acknowledge receipt, move the task back to in_progress, and notify the principal. Usage — /aw-revise <task-id> ["what you plan to do"]

Show a full AgentWeave collaboration overview — session state, all tasks by status, per-agent inboxes, and watchdog health. Use this to understand what is happening across the entire session.

Sync the AgentWeave project context — regenerate all agent context files (CLAUDE.md, AGENTS.md, GEMINI.md) from the source at .agentweave/ai_context.md. Run this after editing ai_context.md to make sure all agents see updated context.

Release a new version of AgentWeave — auto-detects next version, bumps pyproject.toml files, checks if documentation needs updates, updates CHANGELOG and README, commits, pushes and creates GitHub releases via Windows PowerShell (which holds git/gh credentials), then monitors the build. Never invoke this automatically.

Check GitHub Actions CI build status for AgentWeave (publish.yml → PyPI, hub-image.yml → Docker, ci.yml → tests/lint/type-check). Usable standalone with /loop or callable from other skills. Accepts optional tag filters (e.g. "v0.10.0 hub-v0.4.0"). ci.yml is always shown from the latest master push regardless of tag filter.