القائمة
Mark the current Argus task as complete. Use when the work for the current worktree is done and the user wants the task to transition to the "complete" status.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
The hera plan-DAG: author staged, dependency-ordered multi-worker plans inside an argus sandbox and let the daemon gater materialize each node into a born-bound worker as its blockers finish. Load this (in addition to the base `hera` skill) when you are a coordinator and the work decomposes into multiple hera worker units that have DEPENDENCIES among them (one stage needs another's output, or a required ordering) — internal dependencies are the clean signal to plan a DAG rather than spawn workers ad hoc. Covers the authoring/mutation verbs, gating-on-`done`, automatic branch-stacking and its fan-in footgun, short-id node naming, sub-coordinator nodes, and the self-guard prompt patterns. NOT for non-argus sessions; NOT for in-session ephemeral work (use Claude's native sub-agents); NOT for independent workers with no ordering (just spawn them).
Inside an argus sandbox (cwd under ~/.argus/worktrees/ or ARGUS_TASK_ID set), coordinate multi-agent work via hera's mcp__argus__hera_* tools — bootstrap an orchestrator, claim or attach a worker/freelance role, spawn workers, and message roles over the idle-gated bus. Load this skill when you are (or are becoming) a coordinator, when you're spawned as a hera worker, or before delegating work that must run as its OWN argus session (separate worktree / long-running agent / own PR / own sandbox) — as opposed to in-process Claude sub-agents, which stay the right tool for ephemeral in-session fan-out. For staged or dependency-ordered multi-worker plans, this skill routes you to the companion `hera-plan` skill. NOT for non-argus sessions, where these MCP tools are not registered.
The hera plan-DAG: author staged, dependency-ordered multi-worker plans inside an argus sandbox and let the daemon gater materialize each node into a born-bound worker as its blockers finish. Load this (in addition to the base `hera` skill) when you are a coordinator and the work decomposes into multiple hera worker units that have DEPENDENCIES among them (one stage needs another's output, or a required ordering) — internal dependencies are the clean signal to plan a DAG rather than spawn workers ad hoc. Covers the authoring/mutation verbs, gating-on-`done`, automatic branch-stacking and its fan-in footgun, short-id node naming, sub-coordinator nodes, and the self-guard prompt patterns. NOT for non-argus sessions; NOT for in-session ephemeral work (use Claude's native sub-agents); NOT for independent workers with no ordering (just spawn them).
Inside an argus sandbox (cwd under ~/.argus/worktrees/ or ARGUS_TASK_ID set), coordinate multi-agent work via hera's mcp__argus__hera_* tools — bootstrap an orchestrator, claim or attach a worker/freelance role, spawn workers, and message roles over the idle-gated bus. Load this skill when you are (or are becoming) a coordinator, when you're spawned as a hera worker, or before delegating work that must run as its OWN argus session (separate worktree / long-running agent / own PR / own sandbox) — as opposed to in-process Claude sub-agents, which stay the right tool for ephemeral in-session fan-out. For staged or dependency-ordered multi-worker plans, this skill routes you to the companion `hera-plan` skill. NOT for non-argus sessions, where these MCP tools are not registered.
Manage recurring or one-shot tasks in the local Argus daemon via its HTTP API. Use when the user wants to schedule a task locally in argus, create a cron-driven task, fire X every weekday/hour/morning, fire something once at a specific future time (one-shot via run_once_at), set up an agent that needs local filesystem access (logs in ~/.argus, local databases, dotfiles), list or update existing argus schedules, or run an argus schedule now. Distinct from /schedule, which creates remote cloud routines without local access.
| name | argus-complete |
| description | Mark the current Argus task as complete. Use when the work for the current worktree is done and the user wants the task to transition to the "complete" status. |
| allowed-tools | mcp__argus__task_complete |
Mark the Argus task owning the current worktree as complete. This sets the task's status to complete and stamps EndedAt. It does not stop a running agent session — if an agent is still attached, the user should stop it separately first.
This skill is not the same as /archive. /archive moves the task into the Archive section (a visibility flag, independent of status). /argus-complete transitions the workflow status to complete. Use /argus-complete when the work is finished; use /archive (separately, optionally) if you also want it removed from the active task list.
pwdCall the mcp__argus__task_complete MCP tool with the working directory from the Context block above as the cwd argument:
mcp__argus__task_complete(cwd: "<pwd from context>")
Argus resolves the task from cwd by matching it against task worktree paths — the agent process does not know its own task ID, so cwd is the required hand-off.
Do not pass id — the agent has no reliable way to know it.
After the call, report the tool's response verbatim in one line. If the tool errors (e.g. "no task matches cwd"), show the error and stop; do not retry with guessed arguments. If the response says the task is already complete, surface that as-is and stop.